Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "npm update -g"
-
Mood:
- Currently coughing my lungs out, I'm not working tomorrow to keep my colleagues safe
- Cat is purring on my shoulder
- Listening to some dope ass synthwave
- Updating the JetBrains IDEs so that I can work on something to busy my mind
- It's 3:45 AM.4 -
FFS, I wasted my time reinstalling nodejs just to update my npm and tried npm i -g npm.
Outputs a success status but when I check via npm -v it's still the same old version.
Or maybe I'm just too dumb that I don't know how to do it right.10 -
I have officially decided to use CI (Jenkins) at work because "apt-get update && apt-get upgrade -y && composer self-update && composer update && npm update -g && npm update && bower install --allow-root && gulp" after a pull doesn't seem healthy 😂2
-
Are you kidding me? windows-build-tools developers does not know that devs like me would run npm update -g from a standard user account? Don't tell me that they use system administrator accounts for their day to day dev and qa tasks1
-
You cannot upgrade npm via `npm update npm -g` inside a docker container. Yet one can download a npm install skript that performs the installation of the latest npm update ...
Why!?