> It's very important to use strictly given NodeJs version. There were already few reports that after JS recompilation the project started to act strange. After further analyse it came out that this was caused due to using the latest available Node.
I hate to bring node-bashing to this thread, but this further cements my dislike for the platform. I don't know why, but this happens much more often with node than Python or most other languages.
JS (and as such, node) developers seem to love breaking everything down into little tiny bits and then having enormous dependency fan-outs for everything.
With so many different parts written by different people, the likelyhood that any project with have a part that can be affected by any eratta change increases substantially.
------
I have a casual hypothesis that each person tends to settle with a subset of each programming language that they deeply internalize. As such, unless that one person is deliberately trying to, they're unlikely to write code that hits lots of the odd implementation corner cases that are natural in any language/implementation.
However, the subset each person settles on is different, so if you don't have some sort of overarching style/quality management, you will trend towards a project being sensitive to any change in any implementation corner as you increase the number of dependencies.
Dependency management (and possibly more critical, dependency quality) is becoming more and more important as things become more complex, and the tooling is not keeping up either.
I hate to bring node-bashing to this thread, but this further cements my dislike for the platform. I don't know why, but this happens much more often with node than Python or most other languages.