search

crypti / ccoin

:part_alternation_mark: Convert and fetch the cost of over 1000 cryptocurrencies within your terminal, and save repeated queries
MIT License
23 stars 1 forks source link

publish to npm #2

Closed radiovisual closed 7 years ago

radiovisual commented 7 years ago

version 0.0.1 is currently working, so now it just needs to be published to npm.

brh55 commented 7 years ago

Going to publish under crypti org so we both have publish access. What is your npm username?

radiovisual commented 7 years ago

What is your npm username?

Same as my github username: radiovisual

https://www.npmjs.com/~radiovisual

brh55 commented 7 years ago

First time using an org, but I have invited you

radiovisual commented 7 years ago

awesome. I just tested it, and I was able to publish to npm. So this issue can be closed now. Thanks!

brh55 commented 7 years ago

@radiovisual can you try publishing with npm publish --access public ?

radiovisual commented 7 years ago

@brh55 , done! I had to bump to 0.0.2 to publish again.

brh55 commented 7 years ago

@radiovisual Interesting so it appears when it's "org" scoped you need to do npm install @crypti/ccoin. Wondering if it could still be called ccoin, but publish to the org?

brh55 commented 7 years ago

Actually thinking about it, it's probably a good thing as it indicates that the package is from that particular org.

radiovisual commented 7 years ago

Hm. there should be a way around that, since when I install things that are part of an org, like AVA (which is avajs/ava) and lodash (which is in lodash/lodash), I only have to do:

$ npm install --save ava
$ npm install --save lodash

and not:

$ npm install --save @avajs/ava
$ npm install --save @lodash/ava

but I don't necessarily mind the org prefix, I just don't see it out in the wild very often. I can look into a little later. This is my first time publishing under an org, so I have a little bit to learn on that front.

radiovisual commented 7 years ago

its probably just a setting on npm because we transferred ownership of these previously-published and previously-scoped packages

brh55 commented 7 years ago

Looks like in @ava + package.json, they publish as a ava and probably transfer it through the npm website, similarly to what I did for eth-price? I'll take a look as well when I'm off work 👍