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
I run the backend using the nodemon plugin, and passed it the enable-source-map flag so that nodejs reads the generated webpack maps. Now stacktrace will be displayed correctly, but it will contain the webpack:/// path.
To avoid this, I changed the output part of the configuration webpack.config.js
By creating a Callback function in the parameter devtoolModuleFilenameTemplate, and I return a string like files:///full/path/to/file I am using nodejs 16 lts so --enable-source-map works well, this flag appeared in node js 12
Surprisingly, now stack trace and debug (in vs code) work fine, with a path that does not contain webpack:///
Now I don't need node-source-map-support plugin, and I can completely abandon its use, leaving only node js native source map.
when webpack compiles sourcemaps, the urls look like this
webpack:///./foo/bar/some/file.js
is there a way to tell source-map-support, how to map webpack:/// files ?
The text was updated successfully, but these errors were encountered: