Such change would affect the entire project, not just dependency, which would be a very very bad thing to apply to any project (do I need to explain why? - short answer is because other dependencies normally use "engines.node" restriction by purpose). So one could say that you are simplifying your processes at the expense of Both yarn and npm have support for ignoring engine requirements, so you should be able to rely on those if you would like to use these unsupported versions in your development. I understand that introducing so strict node version restriction of course might make the processes at easier but it will likely cause other teams/engineers to waste for no real reason thousands of man-hours in summary to adopt the restriction. These things, of course, can be named "production" at but it doesn't turn them into production things for the rest of the projects that consume as one among other dependencies. Here is the official word from Angular on current version: 'Angular requires a current, active LTS, or maintenance LTS version of Node.js.' In the notes you will see a link to a package.json file that contains an 'engines' section. Those are development things by definition. It uses node in the language service and compiler (as well as the linker) I now feel guilty for giving a hint by referring to node's note at 😄
In many ways this is our "prod" environment.
0 kommentar(er)
