You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] Regression
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
nest start always start in debug mode due to unsafe checks
Options contain even not initialized values:
@kamilmysliwiec, I'm looking into this and trying to fix my bug, but I am a bit confused. Even if I do nest start --debug, options still looks like this:
I'm submitting a...
Current behavior
nest start
always start in debug mode due to unsafe checksOptions contain even not initialized values:
So next check is false-positive
nest-cli/actions/start.action.ts
Line 140 in c745366
also, this one is suspicious
nest-cli/actions/start.action.ts
Line 62 in c745366
Expected behavior
--debug
or--debug-brk
options control thatMinimal reproduction of the problem with instructions
Seems to be broken in #592
Simply make
npm i
in https://github.com/nestjs/nest/tree/master/sample/12-graphql-schema-first or any other sampleWhat is the motivation / use case for changing the behavior?
Environment
The text was updated successfully, but these errors were encountered: