Running npm outdated show latest 1.2.5
See original GitHub issueWhen I run the npm outdated
it shows current/wanted as 1.2.6 but lists 1.2.5 as the latest.
"devDependencies": {
"purify-css": "1.2.x"
}
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
npm-outdated
Description. This command will check the registry to see if any (or, specific) installed packages are currently outdated. By default, only the direct ......
Read more >npm@5 outdated -g shows nothing · Issue #16840 - GitHub
So basicly current version (5.0.x) of npm is totally not functional. Had to downgrade. PLEEEEEEEASE fix ASAP. The world depends on you guys....
Read more >node.js - npm update does not do anything - Stack Overflow
Running npm outdated will allow you to check all the packages that need to be updated. The list will show current, wanted and...
Read more >How to fix security vulnerabilities in NPM/Yarn dependencies
Show only potential vulnerabilities in your dependecies: npm audit. Execute vulnerabilities fix mechanism: npm audit fix.
Read more >All Docs - npm 中文文档
This will install the latest official, tested version of npm. ... This can cause permissions errors when you attempt to run packages globally....
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
Maintainers: if you want to fix this issue, here’s a handy one-liner you can run:
Cheers 😛
+1. The wrong version is annoying.