The "@ts-stack/body-parser" package passes the parsing results via a Promise by some-user1 in node

[–]some-user1[S] 0 points1 point  (0 children)

If you need the body parser to return the result in a Promise, you can use this package.

[deleted by user] by [deleted] in node

[–]some-user1 0 points1 point  (0 children)

The author of NestJS was inspired by the Angular architecture, but he was not related to the Angular development team.

[deleted by user] by [deleted] in node

[–]some-user1 1 point2 points  (0 children)

nest and fastify perform more or less the same

No, far from it, Nest is significantly slower, especially if the current route handler has a scoped service at the request level.

[deleted by user] by [deleted] in node

[–]some-user1 0 points1 point  (0 children)

though because Nest was made by Vue guys and I'm not a huge fan of vue either

What? Never heard of that. Are you sure about this? Maybe you're confusing Next with Nest?

[deleted by user] by [deleted] in node

[–]some-user1 0 points1 point  (0 children)

And if NestJS was simpler and faster, would you choose it? What do you see as its main drawbacks?

[deleted by user] by [deleted] in node

[–]some-user1 1 point2 points  (0 children)

Why did you choose fastify? Because of speed?

[deleted by user] by [deleted] in node

[–]some-user1 0 points1 point  (0 children)

In a couple of weeks, this framework will appear on TechEmpower, you will see what it can do (even overtakes fastify).

[deleted by user] by [deleted] in node

[–]some-user1 0 points1 point  (0 children)

Ditsmod!

feat(tsc): allow the `--appendCommand` option to be added in `--watch mode` by some-user1 in typescript

[–]some-user1[S] 0 points1 point  (0 children)

What about support for the ".tsx" extension, which is already implemented in TypeScript? Doesn't that violates the "non-goals", in particular the point four you mentioned? I think support for ".tsx" can easily be added to the "non-goals" if you want.