React, Flux, GraphQL, Hack, HHVM...? All of this and more!
However there are signs of age in the Node.js ecosystem. Some of the most popular packages and projects like Express.js and Sails have been effectively abandoned and left rotting for years now. This is not helped by a standard library that leaves a lot to desire.
Dahl kicked off Deno in 2018 and the project has kept on improving since then. It is now maturing and a v1.0.0 release is scheduled for May 13 2020 to coincide with the second anniversary of the project. A venerable ecosystem has also sprang up with projects web framework Servest, that integratest with the industry standard React.js view library and a SQL migration framework Nessie.
It will take some time for Deno to catch up with the Node.js ecosystem (and acceptance even in enterprise IT), but it certainly has a lot going for it - it is a unique opportunity to fix the mistakes that weigh Node.js down while also promoting a non-centralized package model leading to centralization of control and allowing for events like the left-pad disaster.
How many years off are we from Node.js projects being projects that developers want to avoid? Is Node.js the horrible J2EE Java or Cobol tech platform that everyone makes jokes about? Could be.Tweet