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
The concept of using source map as a source of truth about the module boundaries in the final bundle was... not the best one. There is a code which does not originate from the source code. It's added during the compilation process, ex. by Babel.
It exists in mappings returned by source map consumer, but both source and originalLine are null. Source Map Explorer presents that code as no source.
The concept of using source map as a source of truth about the module boundaries in the final bundle was... not the best one. There is a code which does not originate from the source code. It's added during the compilation process, ex. by Babel.
It exists in mappings returned by source map consumer, but both
source
andoriginalLine
arenull
. Source Map Explorer presents that code asno source
.Maybe it's a time to switch the strategy and follow what Webpack Bundle Analyzer does.
The text was updated successfully, but these errors were encountered: