Closed kkerr1 closed 7 years ago
This also begs the question of "what is the real code size?"
Would it be too interventionist of a solution to just have webpack-dashboard set devtool: false
?
For inspectpack
and the current issue here, we should still make this not break. But the code size value is totally inaccurate when there's a sourcemap wrapped around the whole thing... Definitely need to document what's up with that...
It seems like overriding a user's selected devtool when webpack dashboard is pretty heavy-handed. I put up a ☝️ proposed short and sweet fix that just tweaks the existing parsing cleanup regex.
In terms of "real code size" it seems that any inline sourcemaps bits will be included in the code
metric but stripped out in minified metrics, which is accurate as far as I can think about it. But, perhaps there is something I am missing?
Fixed in #35
When inspectpack tries to calculate minified/gzipped sizes for a bundle that is created with the
devtool
option set toeval
uglify trips over the embedded sourcemapping info and throws an error likeFor most standalone inspect pack uses this could simply be documented, but it may be a bigger problem for webpack-dashboard users. It may be possible to cleanup in
toParseable()