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
-
Read the changelog. If there's none, go to the Github and look at the changes in the files. If that doesn't work, find a replacement because you chose the absolute worst version of at least 10 versions of the same functionality.
Lock your versions in prod.
Go learn NPM. Read all the guide... please! There's a really fucking good reason babel has changed their naming scheme.
Educate yourself. -
@Kandelborg You, guys here are so polite, I like that ;D
Actually, of course I'm always educating myself, but when it is possible to kill your production app just by trying to update dependencies - it is a real pain in the ass. (and it almost always does so)
Or another example: you were running "npm install [list of packages you project requires]" yesterday, and then just started to write your code.
But today it is not working anymore! Something in a list of 15-20 dependencies causes it to fail. And you either spend hours of finding what, or just end by copy-pasting your old config to stick to older versions and never update.
That is a frustration indeed, and it continues to happen. -
@Argos I agree. I've recently spent more than 30 hours over a couple of weeks just to update various packages.
The terser thing.. I've investigated a bit and semver hasn't been followed and that's the issue. Mostly because he isn't part of the webpack team and they chose to utilise his package anyways. It's almost a perfect recipe for disaster.
What only relying on JavaScript for HTML form input validation looks like
Found something true as 1 == 1
Why does everything installed via npm sux so hard?
Why the fuck does any minor update in their bullshit packages either forces you to change config files:
E.g. now should be "@babel/core" instead of "babel-core" - WHAT A FUCKING SIGNIFICANT CHANGE!!! Rewrite all you configs motherfucker, that goddamn "@" in front of our shit is SO IMPORTANT that we will break everything to add it
Or breaks the code internally:
Consider the recent fail of fucking Terser [https://github.com/gatsbyjs/gatsby/...] that breaks fucking webpack and FORCE YOU TO ROLLBACK TO ANY VERSION THAT WORKS, why you nerd retards, can not run a simple dummy project BEFORE YOU RELEASE YOUR SHIT???!?!!?
Why any fucking update from *.*.1 to *.*.2 turns into hours of googling of what the fuck got broken this time??
The way that webpack, babel and other npm packages are released nowadays is absolutely retarded. I really have a strong feeling that it is better to keep old error-proof working config and NEVER UPDATE, than constantly suffer from butthurt
p.s.
Of course I am sorry for all the hate and caps in my post, and have respect for guys that develop amazing stuff for us for free, but I need to share this
rant
js
javascript
react
babel
npm
webpack
node