5 ms·

Honestly typeorm and nestjs are pretty bad.

• navaneethpk 5y ago
  TypeORM has a lot of issues but in our case it hasn't caused any major blockers. Most of the time the issue is with documentation and sometimes you run into issues like this: https://github.com/typeorm/typeorm/issues/316 https://github.com/typeorm/typeorm/issues/316. NestJS on the other hand is very solid. It has good documentation and a good community. We haven't faced any issues with NestJS yet.
• 88913527 5y ago
  NestJS has some pretty horrific default settings, like a max 1MB request payload size. And you have to write custom content-type processors for anything other than 'application/json'. So if you're doing say, file upload's over 1MB, you already have to make 2 configuration changes. But you wouldn't assume that OOTB 1 MB file upload isn't supported for what claims to be a full nuts-and-bolts web application framework.
  • lcrz 5y ago
    > a max 1MB request payload size How would that be a bad default, when it's probably more than sufficient for 99% of the use cases out there? It's even the same default as nginx: https://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size https://nginx.org/en/docs/http/ngx_http_core_module.html#cli... Nest.js is clearly targeting JSON-based CRUD apps, and the defaults are pretty good. File uploads through JSON is not as simple a problem as you try to make it. Are you using bas64 encoding and embedding it in the JSON? Are you using multipart/form-data?
• jeremycarter 5y ago
  With all its warts NestJS is still a great choice if you want everything to be well structured with a touch of "enterprise grade" - whatever that means. Compliment it with an Angular front end and you've got a frontend and backend with very similar structure.