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
-
@magicMirror it was on 3 different projects. One time git brash froze during update and killing the process half-installed it. Another time just running update software (a requirement) broke it, and another time I guess a package required a higher version than I had and updating it the normal way failed because it didn't properly uninstall an old version
-
@magicMirror gotta agree. @crazed I gave you ++ cause this is a proper rant but I have not experienced such instability with npm or node across several deployed systems
-
@magicMirror yeah npm shouldn't do that...
-
@jeeper @DucksCanCode before this past week I had no problems, maybe its just a mixture of other things causing npm to fail, like git bash siezing up when getting npm@latest
-
@Crazed sounds like incredibly bad luck....
-
@magicMirror wouldn't be a first 😀
-
@Crazed what OS are you on?
-
Me: does literally anything
Npm: breaks
Why NPM? Why must you do it? This is the third time this week on a third system. I just wanted to update so my packages would work. But nooooooo. Oh you wanna update? It'd be a real shame if I, I don't know, didn't update properly whatsoever and all of a sudden couldn't find any internal modules I need to run.
"Just use npm i npm@latest"
Yeah I would except for the whole I can't use NPM at all thing. even npm -v breaks. Can't find internal module. So I literally have to wipe eveey trace of npm/node and do a clean install.
It's so frustrating! I can't do any work because I spend all my damn time fuckin around with NPM.
rant