nrwl / nx

Smart Monorepos · Fast CI
https://nx.dev
MIT License
23.62k stars 2.36k forks source link

NestJS/Crud, how to diable webpack to be compliant? #3520

Closed fstn closed 4 years ago

fstn commented 4 years ago

I'm trying to add nest/crud to my Nestjs app on a nrwl nx workspace.

When I try to serve my app, I get:

TypeError: Cannot read property 'name' of undefined
    at CrudRoutesFactory.get modelName [as modelName] (/Users/ss/ecandidaturev2/ecandidaturev2/node_modules/@nestjsx/crud/src/crud/crud-routes.factory.ts:45:36)
    at CrudRoutesFactory.mergeOptions (/Users/ss/ecandidaturev2/ecandidaturev2/node_modules/@nestjsx/crud/src/crud/crud-routes.factory.ts:123:75)
    at CrudRoutesFactory.create (/Users/ss/ecandidaturev2/ecandidaturev2/node_modules/@nestjsx/crud/src/crud/crud-routes.factory.ts:66:10)
    at new CrudRoutesFactory (/Users/ss/ecandidaturev2/ecandidaturev2/node_modules/@nestjsx/crud/src/crud/crud-routes.factory.ts:33:10)
    at Function.create (/Users/ss/ecandidaturev2/ecandidaturev2/node_modules/@nestjsx/crud/src/crud/crud-routes.factory.ts:37:12)
    at /Users/ss/ecandidaturev2/ecandidaturev2/node_modules/@nestjsx/crud/src/decorators/crud.decorator.ts:5:35
    at DecorateConstructor (/Users/ss/ecandidaturev2/ecandidaturev2/node_modules/reflect-metadata/Reflect.js:541:33)
    at Object.decorate (/Users/ss/ecandidaturev2/ecandidaturev2/node_modules/reflect-metadata/Reflect.js:130:24)
    at Object.__decorate (/Users/ss/ecandidaturev2/ecandidaturev2/node_modules/tslib/tslib.js:96:96)
    at Object../apps/back/src/candidate-files/controllers/candidate-file.controller.ts (/Users/ss/ecandidaturev2/ecandidaturev2/dist/apps/back/webpack:/apps/back/src/candidate-files/controllers/candidate-file.controller.ts:54:37)
No type errors found

By looking at other issues, I can see that it's link to webpack, do you know how I can manage this?

How can I disable webpack or turn crud into webpack compliant?

github-actions[bot] commented 1 year ago

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.