v3.3.12 listed as released but has not been published to public npm registry
See original GitHub issueDescribe the bug v3.3.12, which fixes a low vulnerability by updating the yargs dependency, is listed under releases but the npm registry still shows 3.3.11 as the latest version
What is the current behavior?
v3.3.12 is unavailable via npm install
To Reproduce
npm install webpack-cli@3.3.12
- Notice “No matching version found” error
Expected behavior v3.3.12 can be installed
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Package is not publishing to npm (not in the npm registry)
Try npm login . In case of npm publish , sometimes misleading message is shown.
Read more >npm-publish - npm Docs
Description. Publishes a package to the registry so that it can be installed by name. By default npm will publish to the public...
Read more >Upgrading Your Maps JavaScript API Application from V2 to V3
The Maps JavaScript API v2 is no longer available as of May 26, 2021. As a result, your site's v2 maps will stop...
Read more >node - Official Image | Docker Hub
Node.js is a JavaScript-based platform for server-side and networking applications.
Read more >What's New In Python 3.11 — Python 3.11.1 documentation
Support broke sometime between Python 3.2 and 3.6, with no one noticing until after Python 3.10.0 was released. In addition, bringing back support...
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 Free
Top 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
today/tomorrow
Done, sorry for delay