A JavaScript Nightmare
blog.ignaciobrasca.com
A JavaScript Nightmare
1–10 of 101 posts
Re: A JavaScript Nightmare
#2Does C not have these issues?
Re: A JavaScript Nightmare
#3Shouldn’t you use fixed versions and use something like ‘npm ci’ to install the exact dependency tree?
Feels more like an oversight from the developers rather than a JavaScript problem.
When you want to upgrade, only then do you run all regression tests and do so.
Re: A JavaScript Nightmare
#4[flagged]
Re: A JavaScript Nightmare
#5[flagged]
To be fair, JavaScript is harder that most people think, the problem is that everyone thinks they are an expert, so we end up with this kind of problems.
There is a lack of engineering discipline and too much hacking!
Re: A JavaScript Nightmare
#6This was posed 20 hours ago: https://news.ycombinator.com/item?id=39724247
Not sure why I can't downvote articles, ah well.
Re: A JavaScript Nightmare
#7tldr: A dependency wasn't pinned, the dependency changed, and stuff broke. Author thinks Javascript sucks.
I will say this though: it is infuriating that package managers (every single one I've used, not just NPM) don't default to pinning exact dependency versions, and instead let it "automatically" update minor versions.
Re: A JavaScript Nightmare
#8> not using TypeScript for any serious product
Well, here is your problem.
Re: A JavaScript Nightmare
#9[flagged]
>> walking down the road
>> ground suddenly became air out of nowhere
> Lol, skill issue!
Re: A JavaScript Nightmare
#10tldr: A dependency wasn't pinned, the dependency changed, and stuff broke. Author thinks Javascript sucks. I will say this though: it is infuriating that package managers (every single one I've used, not just NPM) don't default to pinning exact dependency versions, and instead let it "automatically" update minor versions.
The package wasn't following semantic versioning. Only major versions should introduce breaking changes.