Ranter
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
Comments
-
I decided to add a comment for each 5 failed attempts to build my new team's npm packages, today.
Let's see how much we will have today evening.
xD -
Finally! Solved it!
The option --no-bin-links is no longer a live saver when it comes to Windows + Docker.
Since it is, in most cases, no longer needed, we killed this option.
After that still got some untar unpack bullshit.
Than npm cache clean --force
Boom! Got it! -
Fuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuck!
It stabbed me in my ducking back.
docker npm solution works for my VM configuration, but ends up with errors on my colleague's machine.
I bet we have to update the docker dev vm stack on each of my colleagues machines.
Fuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuun! -
Of course it's not over, yet.
Turns out the only successful run of npm install on my machine happened, because the company's anti-vir client wasn't checking my i/o access for a couple of minutes.
Today it wasn't possible to execute a successful npm run with Windows + Vagrant + Docker, because a bunch of different i/o errors occurred.
Finally I created a ticket for company's IT Support to check the former classification of dev folder pattern as trustworthy.
I know there was a anti-vir configuration for that.
It seems like this configuration got lost over the time.
Fml : /
Luckily we have another sprint week to get control over that mess! -
We finally managed to get the npm builds executed on every machine of our team.
We finally raised the node version from 6.14.2 on 8.11.3.
The from time to time npm errors reduced to a bearable amount....
npm...............
Related Rants
-
cdrice105"You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!" ...
-
MoboTheHobo35My Friend: Dude our Linux Server is not working anymore! Me: What? What did you do? My friend: Nothing I swe...
-
tommy15Right now someone at Google is coding something useless for us to laugh at on April Fools.
npm you dank pile of shit!
After updating npm I get "Maximum call stack size exceeded" when I use npm install --no-bin-links as usual.
After searching a solution for this shit it seams like the npm devs fucked around with the --no-bin-links option, since this nasty error message vanishes if one downgrade npm.
These goddamn assholes.
Keep your filthy fingers off this option, since it is essentially for windows devs!
rant
--no-bin-links
deep hate for npm
windows
downgrade
update
fml
npm