NPM Publish
See original GitHub issueI’m excited to start using this library, but I need to use the isPlural()
function from v5.1.0 which is not available in NPM (latest is 5.0.0). Would you mind publishing the latest to NPM, please?
Thanks! Ben
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
npm-publish - npm Docs
Publishes a package to the registry so that it can be installed by name. By default npm will publish to the public registry....
Read more >npm-publish - npm Docs
Publishes a package to the registry so that it can be installed by name. All files in the package directory are included if...
Read more >Creating and publishing scoped public packages - npm Docs
Publishing scoped public packages ; On the command line, navigate to the root directory of your package. cd /path/to/package ; To publish your...
Read more >Creating and publishing private packages - npm Docs
On the command line, navigate to the root directory of your package. cd /path/to/package ; To publish your private package to the npm...
Read more >Contributing packages to the registry - npm Docs
Contributing packages to the registry. Creating a package.json file · Creating Node.js modules · About package README files · Creating and publishing ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@blakeembrey yes I was using my company’s registry at the time, and it has a 24h cache period. I’ll be sure to bypass it next time I run npm info. BTW I’m now using change-case as well, these are awesome libraries! Thank you!
Sorry about that, it was indeed cached (I did run npm info just prior to opening the issue). I can see 6.0.0 now.