Switch stable version on NPM
See original GitHub issueIt looks like updating NPM when making a release stable does not yet work, even though we looked into this before. I made version 2.4.456 stable today, but NPM still shows version 2.3.200. What did work is updating the next
tag for pre-release 2.5.207, so it looks like the release script doesn’t handle release updates correctly in contrast to release creations which work.
Please find the cause of this, and for now update the latest
tag on NPM to version 2.4.456 manually.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
How can I change the version of npm using nvm?
In order to change your npm version when using nvm, you must install your npm version only inside the folder of ...
Read more >Try the latest stable version of npm
Option 1 or 2. Go into %ProgramFiles%\nodejs\node_modules\npm and copy the file named npmrc in the new npm folder, which should be %appdata%\npm\node_modules\ ...
Read more >How do I switch NPM versions? · Issue #484 · tj/n
Downgrade NPM version I need NPM < 5.x for support with React Native, I can switch node just fine but I can't seem...
Read more >Switching between Node versions during development
The n command for installing and activating a version of Node is simple: n 6.17.1 . You could also use n latest for...
Read more >npm: How To Install A Specific Version of Node.js Package
By default, the npm install command fetches the latest available version of the specified package—in this case, it's Renovate version ...
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
I update npm again. Thought I used the same command as before but I guess not.
Yes, NPM seems to have some problems with the tag name. Fortunately https://www.npmjs.com/package/pdfjs-dist/v/2.4.456 already exists, we just need to re-push the
latest
tag to fix this.