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
Hello, this is a feature request. With Webpack, it is possible to generate bundled js files along with their sourcemaps without including the original source in the sourcemaps. But the mappings are still present, would it be possible to support a partial, best-effort reconstruction, to make the file more readable and beautified?
What bothers me when reading simple beautified files is the following syntax:
23487: function name {
...
}
I hope I have been clear enough... Any advice would be greatly appreciated!
The text was updated successfully, but these errors were encountered:
In case you are wondering, the source links in the form "webpack://" return 404s. Logic tells me that most of this code can be reconstructed from npmjs.com, and those that are not available publicly, we can use the compressed code "beautified". That would be awesome best effort reconstruction, especially if it can work with the newly supported --preserve option. What do you think?
Hello, this is a feature request. With Webpack, it is possible to generate bundled js files along with their sourcemaps without including the original source in the sourcemaps. But the mappings are still present, would it be possible to support a partial, best-effort reconstruction, to make the file more readable and beautified?
What bothers me when reading simple beautified files is the following syntax:
23487: function name {
...
}
I hope I have been clear enough... Any advice would be greatly appreciated!
The text was updated successfully, but these errors were encountered: