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
-
@black-kite he can't cry. He writes even rust for fun
-
@CoreFusionX yeah we tried on powershell and bash, both had the same issue.
But i also agree, that sometimes one shell works better than another one, i had that numerous times aswell (funnily enough also with npm related stuff, but on the work pc directly) -
Windows has the path length problem, which cannot be fully circumvented.
A registry setting exists, though that only works for newer APIs - thus the inconsistency whether it works or not.
https://learn.microsoft.com/en-us/...
Note that WSL is not full Linux.
Under Linux there are no problems regarding max path length, but NPM is crap tastic.
The things NPM does wrong far outweigh the things NPM does right.
Found something true as 1 == 1
Code I wrote: 15kb
NPM Modules: 198Mb
This is where US's bandwith is going
Today in some onboarding meeting i was laughing my ass off.
We were setting up the development machines that we got from the client to work on via citrix.
You guys probably know, that when you put your npm projects too nested into your filesystem, that packages randomly start not behaving because of too long file names or path names and stuff like that. That seems to be a problem with all OS (to be fair i havent actively looked for a solution, but it happened to me on Windis and Linux, so i'm just assuming here)
but even more so for some packages on Windis, when the project is not running on the same fucking drive letter than where your OS is running on. Like... wtf?
Had two UI5 projects pulled, both of them on D:. The first npm install went through flawlessly, the second one has a number of random errors, me and the other dev didn't know what they were. So what i suggested is to move this project onto C: and try it again. Turns out that was exactly it. Et voila, npm install ran through without any hiccups..
rant
fuckwindis
npm
citrix