I am usually not into framework battles, and I am not a contributor/affiliated, so take this as a sincere opinion of a fullstack js/ts dev. If you are about to jump into js serverside, take the time to evaluate Nest: https://nestjs.com/. Especially if you are coming from a modern SPA (react/angular/vue) background. I find its approach far superior to any js (and non js) backend alternatives I have been so far working with.
On my most recent app, I started with Hapi but was starting to get bothered by the number of "official plugins" that did not include TypeScript typings. After waiting weeks for official Hapi v17 typings to make it into DefinitelyTyped, I gave up and switched to Nest and found it much easier to get started.
For me, the fact that it's written in TypeScript and based on Express (i.e. you can use any Express middleware) was enough to make it more compelling than other options.
Wow, I confused that with Next.js for a moment, which I turn confused with Nuxt.js. Great...
Anyway, it's great that it's written in TypeScript. I couldn't find this with a cursory glance through the docs, but how does this handle the front-end? Can it do server-side rendering, for example, or is that completely separate?
Yes naming is weirdly close to next. Nest is basically an architecture core, think of it as a way to "angularize" (2+) your express app. You can use what library better suits you for any purpose you'd need, e.g., nuxt or pug, for SSR.
Thanks for the suggestion - the framework looks great from a cursory glance. I really like the decorator patterns - I'll use it on my next side project!
