Storytime. When the company I work for hired a person who was super excited about NestJS, I looked at it with an open mind (or so I'd like to think). I was pro

Storytime. When the company I work for hired a person who was super excited about NestJS, I looked at it with an open mind (or so I'd like to think). I was probably a bit sceptical because this person, who seemed really nice, couldn't think of a single thing he disliked about it (that's a question I tend to ask about any tech that someone is all-over-the-moon about, and my thinking is that if you can't list a single thing you dislike about something, you probably don't know it well enough), but let's take a look at it! As soon as I saw they had basically copy/pasted the Angular 2+ module system into Node.js, and went full-hog into IoC, I decided not to even try it out. The same Angular 2+ module system that basically was copy/pasted from AngularJS and that I had actually ripped out of our huge AngularJS app at our previous job because it caused more friction than it solved, and lo and behold, the tests became simpler when we didn't have to use ngMock. All those services were singletons anyway and were more suited to being actual JS/TS modules. But AngularJS had a valid reason for it because it was back in forever-ago and there were no JS modules, much less dynamic imports for code-splitting. Not that you need code splitting for a backend app. I have never felt I needed DI in a Node.js app. NestJS - not even once.