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
devtoolModuleFilenameTemplate option under the output config parameter in webpack can be configured to determine the names/paths of sourcemap files. Default is 'webpack://[namespace]/[resource-path]?[loaders]'. But I choose not to use this default version and instead just use the [resource-path]. ts-loader creates the correct sourceMaps by just including the relative paths of the source files. I would expect css-loader to respect this too.
Actual Behavior
When [resource-path] is used, css-loader only uses the name of the css file. So, the Chrome dev tools cannot find the actual source file. Using the following also confirms this behavior:
Expected Behavior
devtoolModuleFilenameTemplate
option under theoutput
config parameter in webpack can be configured to determine the names/paths of sourcemap files. Default is'webpack://[namespace]/[resource-path]?[loaders]'
. But I choose not to use this default version and instead just use the[resource-path]
.ts-loader
creates the correct sourceMaps by just including the relative paths of the source files. I would expectcss-loader
to respect this too.Actual Behavior
When
[resource-path]
is used,css-loader
only uses the name of the css file. So, the Chrome dev tools cannot find the actual source file. Using the following also confirms this behavior:Relevant Part of webpack.config.js
The text was updated successfully, but these errors were encountered: