4

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!

Comments
  • 2
    npm is such a great tool isn't it 🙃
  • 0
    Nooooooot! ^^
  • 0
    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
  • 0
    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!
  • 0
    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!
  • 0
    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!
  • 0
  • 0
    my comments
  • 0
    for every 5 times
  • 0
    of fails npm builds

    xD
  • 0
    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...............
Add Comment