Nodejs debugger sets break points on wrong location

Hi, I'm working on a node project (TypeScript)
we use webpack and HMR  every thing works fine ,but the debugger sets break points on the wrong files( the compiled  ones) this happens if we change the code and and update occurs , we need to restart the process again sometimes break points don't pause the execution

Is there any suggestion on solving this  issue? thanks :)
* update I tried the same project on chrome dev tools and ti worked there and the source map resolved the updated files to the  original once not on the patch updates

2 comments
Comment actions Permalink

Please can you elaborate on your setup? What does your project look like (frameworks, etc), what web server is it hosted on? Do you debug a client or server code?

0
Comment actions Permalink

It was a Nestjs project , till now i don't know why it was doing this, but it worked with settings the devtool option to eval on Webpack config

It makes the project to fail with Type ORM migrations but have to toggle between source-map and eval from time to time , but at least  it works fine now

 

1

Please sign in to leave a comment.