Skip to content
This repository has been archived by the owner on Aug 1, 2023. It is now read-only.

Publish to NPM #37

Open
yknl opened this issue Mar 26, 2020 · 4 comments
Open

Publish to NPM #37

yknl opened this issue Mar 26, 2020 · 4 comments
Assignees

Comments

@yknl
Copy link
Contributor

yknl commented Mar 26, 2020

Publish to NPM as @blockstack/cli and update installation instructions in the Readme.

@kyranjamie
Copy link

kyranjamie commented Mar 26, 2020

May I waltz in with the suggestion we rename the package to cli, so on npm it's @blockstack/cli ?

Edit: I was going to cite angular's cli package as an example, but they call the repo angular-cli and the package @angular/cli 🤷‍♂

@yknl
Copy link
Contributor Author

yknl commented Mar 26, 2020

@blockstack/cli sounds good to me.

I believe the reason for the weird naming of this repo is due to a previous, now deprecated package called blockstack-cli

@yknl yknl self-assigned this Mar 26, 2020
@jcnelson
Copy link
Collaborator

jcnelson commented Mar 31, 2020

I'd caution against putting this on NPM. This is a developers only tool, and is unsafe for use with the general public or even with developers who aren't familiar with the inner workings of Blockstack. For example, the CLI requires users to enter raw private keys for a lot of operations, and doesn't really stop you from shooting yourself in the foot if you enter the wrong private key(s) or wrong address(es), or enter private keys in the wrong order.

@yknl
Copy link
Contributor Author

yknl commented Apr 2, 2020

We are targeting developers with this tool though. The reason to publish it to NPM is to make it a little easier to install. I don't think we'll see non-developers flock to the tool by publishing it. I think the only thing we're doing here is improving our support for the tool.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants