brews node and its npm outdated command suggest a downgrade #258
Unanswered
ar4hc
asked this question in
Everyday usage
Replies: 2 comments
-
|
You have to use |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Try running |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
i installed node (15) using brew and got a npm with it.
The npm was version 7.0.15,
then strange things happened and i got a npm version 6.14.9.
Did a reinstall of node and had npm 7 again.
checked the installed npms and found this:
# npm -g outdated Package Current Wanted Latest Location Depended by npm 7.0.15 6.14.9 6.14.9 node_modules/npm globalnpm thinks 6 is after 7...
So something "upgraded" my global npm install and got a downgrade instead. Not sure what...
Intellij or some script like depcheck npm-upgrade etc. i think.
the ruby formula did some stuff with the package.json
and i think this could be the problem here.
How can i avoid downgrading my npm here?
Beta Was this translation helpful? Give feedback.
All reactions