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
{{ message }}
This repository has been archived by the owner on May 17, 2019. It is now read-only.
Fusion-cli correctly .map files for production builds, but uses hidden-source-map webpack config, which omits the //# sourceMappingURL comment at the end of the source files.
hidden-source-map - Same as source-map, but doesn't add a reference comment to the bundle. Useful if you only want SourceMaps to map error stack traces from error reports, but don't want to expose your SourceMap for the browser development tools.
For many projects, it's useful to expose hidden source maps to devtools to allow debugging in production.
I'd like to propose an option to use 'source-map' instead if 'hidden-source-map'
The text was updated successfully, but these errors were encountered:
Fusion-cli correctly
.map
files for production builds, but useshidden-source-map
webpack config, which omits the//# sourceMappingURL
comment at the end of the source files.From https://webpack.js.org/configuration/devtool/:
For many projects, it's useful to expose hidden source maps to devtools to allow debugging in production.
I'd like to propose an option to use 'source-map' instead if 'hidden-source-map'
The text was updated successfully, but these errors were encountered: