The introduction of long term support (LTS) for versions of Node.js was a critical event that enabled the wide-spread adoption of the runtime, with up to 70% of developers seeing it as an important feature.
A large part of the value of the Node.js LTS policy is the clarity it gives to users on release schedules and the longevity with which a given version will be supported for critical fixes. Node.js applications, however, consist of significantly more that just the Node.js runtime. Even the most basic Express.js application contains 181 Node.js modules.
While some Node.js modules declare an LTS policy, there is little consistency in what that means, what releases are in LTS, and for how long. This means that users have to monitor and track the LTS policy of all of their individual dependencies and build complex update and migration plans in order to ensure that they are always in a position to receive critical fixes.