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
When magic-string generates source maps for Rollup, it encodes the mappings array into a spec-compliant string, but then rollup immediately decodes it for further manipulation (collapsing stage). If we introduce a non-encoded version of MagicStringgenerateMap, we can eliminate the steps in bold above entirely, cutting the source map step almost in half.
Stand by while I'm working on corresponding PRs.
The text was updated successfully, but these errors were encountered:
Noticed this huge low hanging fruit while profiling source maps:
When
magic-string
generates source maps for Rollup, it encodes the mappings array into a spec-compliant string, but thenrollup
immediately decodes it for further manipulation (collapsing stage). If we introduce a non-encoded version ofMagicString
generateMap
, we can eliminate the steps in bold above entirely, cutting the source map step almost in half.Stand by while I'm working on corresponding PRs.
The text was updated successfully, but these errors were encountered: