Invalid file path reference in stack trace on NODE app with nx serve

Current Behavior

Stack trace errors (NODE APP, nx serve) are referencing incorrect files

Expected Behavior

Stack trace should reference the right path to allow VS CODE to open the file on click.

Steps to Reproduce

On a NODE project, run the app and throw somewhere, you will get a stack trace printed in the console. The paths for ts files are mapped incorrectly due to webpack mapping errors.

Error: 123
    at ServerInitializationModule.configure (/Users/shlomiassaf/Desktop/Code/sg/sg-node/dist/applications/public-api/webpack:/applications/public-api/src/app/server/init/init.module.ts:44:11)
    at MiddlewareModule.loadConfiguration (/Users/shlomiassaf/Desktop/Code/sg/sg-node/node_modules/@nestjs/core/middleware/middleware-module.js:47:24)
    at loadMiddlewareConfiguration (/Users/shlomiassaf/Desktop/Code/sg/sg-node/node_modules/@nestjs/core/middleware/middleware-module.js:37:24)
    at Array.map (<anonymous>)
...

Instead of /Users/shlomiassaf/Desktop/Code/sg/sg-node/dist/applications/public-api/webpack:/applications/public-api/src/app/server/init/init.module.ts

It should be /Users/shlomiassaf/Desktop/Code/sg/sg-node/applications/public-api/src/app/server/init/init.module.ts

It has an effect on the development process, very hard to jump into areas. Not the end of the world, but would be nice to have this sorted out.

Thanks!

[hardikbeladiya]

Same here. I am working on the Project in which we don’t have the clue from where the Error is coming, so I guess this is very important Issue.

[elisiskind]

I agree this should be reopened - this is a serious problem and I am not aware of any workarounds.