Full Stack. Now, that's a dirty composite in some corners and rarely entirely true-- but in some cases... backend (Node) and front-end (let's say React) are not handled by two developers, but one. They might also sing the theme tune. That flexibility regardless of the fat wad of packages, is both profitable (in the short term) and valuable in the long term as a proof of concept. Who develops something and says "that's done, finished, everlasting"? It's useful to have a combined ecosystem in many cases, accessible and friendly to a single, dare I say it, "Full Stack" developer. If it needs to be made better, if it needs refactoring, everything is on the table until it doesn't make sense. If the product works great... if it needs to move away from node, fine. If you build a house that's worth looking at, nobody's thinking about the bricks, but that doesn't mean things should stay as they are.