		@@ -1,1 +0,1 @@
		{"version":"0.0.0","commands":{"hello":{"id":"hello","description":"describe the command here","pluginName":"artsy-cli","pluginType":"core","aliases":[],"examples":["$ artsy hello\nhello world from ./src/hello.ts!\n"],"flags":{"help":{"name":"help","type":"boolean","char":"h","description":"show CLI help","allowNo":false},"name":{"name":"name","type":"option","char":"n","description":"name to print"},"force":{"name":"force","type":"boolean","char":"f","allowNo":false}},"args":[{"name":"file"}]}}}
		{"version":"0.0.1","commands":{"hello":{"id":"hello","description":"describe the command here","pluginName":"artsy-cli","pluginType":"core","aliases":[],"examples":["$ artsy hello\nhello world from ./src/hello.ts!\n"],"flags":{"help":{"name":"help","type":"boolean","char":"h","description":"show CLI help","allowNo":false},"name":{"name":"name","type":"option","char":"n","description":"name to print"},"force":{"name":"force","type":"boolean","char":"f","allowNo":false}},"args":[{"name":"file"}]}}}

package.json

		{
		"name": "artsy-cli",
		"description": "The artsy command line tool",
		"version": "0.0.0",
		"version": "0.0.1",
		"author": "Jon Allured @jonallured",
		@@ -14,5 +14,8 @@ "bin": {
		"@oclif/plugin-help": "^2",
		"@types/node-fetch": "^2.5.0",
		"node-fetch": "^2.6.0",
		"tslib": "^1"
		},
		"devDependencies": {
		"@artsy/auto-config": "^1.0.1",
		"@oclif/dev-cli": "^1",
		@@ -19,0 +22,0 @@ "@oclif/test": "^1",

README.md

		@@ -6,21 +6,10 @@ # Artsy CLI [![CircleCI][badge]][circleci]

		What I'm thinking here is that we mob on creating the oclif tool and then the
		streams of work could be:
		## Install

		* implementing identify against MP without auth
		* research how we'd sign in so that a future refactor could identify with auth
		* we could just create a ClientApplication in Gravity and use those creds
		* we could allow users to sign in/out and grab the JWT for them
		Artsy CLI is published on npm, so installing is really easy:

		The thing about using oauth for a particular user is that it introduces some
		things that we might not want like we try to identify a thing but that user
		doesn't have access to that object. If we use a ClientApplication then that all
		sorta fades away. On the other hand, sometimes I very much DO want to have the
		context of a user because I'm trouble-shooting or something like that. Maybe
		both would be good to support?
		```
		$ npm install --global artsy-cli
		```

		In the end, the ClientApplication is sure faster to get going!

		Another thought is if I want to be going through MP or Gravity.

		## Releasing
		@@ -27,0 +16,0 @@

artsy-cli - npm Package Compare versions

New alerts