Showing posts from 2018

npm, I'm not ready for a commitment

Hi aron.helser! A new version of the package react-tooltip (3.4.3) was published at 2018-04-11T15:16:48.128Z from . The shasum of this package was 449531f1758487c5fbb2abf812fd8b 7a89a506cf. If you have questions or security concerns, you can reply to this message or email . npm loves you.

Web tools: semantic-release and npm organizations

I like continuous-integration,  Travis  and semantic-release . They make new code available immediately, after automated testing. I'm working on VeraInView , and I hit a snag I wanted to note. Normally, if you set up Travis and end with 'npm run semantic-release', it will publish your new module to NPM. However, with this project I got a 'forbidden' error returned from NPM. I am using an Org  for this project, so its package name is @doe-casl/verain-view. That namespace means that the package is by default private, and as a result 'npm publish' defaults to private - which requires a paid npm account. The solution is to publish your package manually the first time: npm publish --access public --tag 1.0.0 I left off the --tag argument, and ended up with the first version being '0.0.0-semantic-release', which is why I added it above. Hope that helps!