I can understand doing this from a maintainer point of view - I'll bet this gets written in a better way using the lessons learned from the first version. Movi

I can understand doing this from a maintainer point of view - I'll bet this gets written in a better way using the lessons learned from the first version. Moving fast and breaking things seems par for the course in javascript land, I don't really try to keep up. I've ended up only using NodeJS for plumbing type apps (e.g. web hook listeners calling other APIs), definitely not for full on web apps, which I've found too-easily devolve into a mess of code. Keeping up with anything in the NodeJS community is hard - from Node/NPM itself to all the OSS projects around it. I still use it, but I do definitely make fun of how often I'm destroying the node_modules directory and npm installing "fresh" due to the weirdest errors.