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
Let's say there is a npm package that ship with some compiled js:
pkg
|-- index.js
|-- index.js.map
When this package is imported by some source code, rspack automatically pick up the .map file, which is awesome.
However in some cases source maps in the package are not usable enough. That may caused by having full path in the map, or having "webpack://" prefix in the paths, or the map is corrupted. And when analyzing package size with source-map-explorer, the input source map may make its result harder to read, since I'm looking into the source sizes of a package that I don't care.
It's something like webpack without source-map-loader. Is there anyway to achieve this? Thanks a lot!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Let's say there is a npm package that ship with some compiled js:
When this package is imported by some source code, rspack automatically pick up the
.mapfile, which is awesome.However in some cases source maps in the package are not usable enough. That may caused by having full path in the map, or having "webpack://" prefix in the paths, or the map is corrupted. And when analyzing package size with source-map-explorer, the input source map may make its result harder to read, since I'm looking into the source sizes of a package that I don't care.
It's something like webpack without source-map-loader. Is there anyway to achieve this? Thanks a lot!
Beta Was this translation helpful? Give feedback.
All reactions