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
For most JS apps, the vast majority of bundled code is library dependencies of the app, not code written by the app developer. Most of those libraries are published in the NPM registry.
Can these two facts be leveraged to dramatically shrink the size of app sourcemaps by pointing to external URLs for library sourcemaps instead of including library sources in app sourcemaps?
If yes, then does that scenario work today, using current bundlers, build tools, and debuggers?
If not, what would need to change to make it work?
I know the long-term goal is to completely decouple sourcemap download from code download, but I'm wondering if enabling JIT library sourcemap downloads might be a useful intermediate step.
The text was updated successfully, but these errors were encountered:
For most JS apps, the vast majority of bundled code is library dependencies of the app, not code written by the app developer. Most of those libraries are published in the NPM registry.
Can these two facts be leveraged to dramatically shrink the size of app sourcemaps by pointing to external URLs for library sourcemaps instead of including library sources in app sourcemaps?
If yes, then does that scenario work today, using current bundlers, build tools, and debuggers?
If not, what would need to change to make it work?
I know the long-term goal is to completely decouple sourcemap download from code download, but I'm wondering if enabling JIT library sourcemap downloads might be a useful intermediate step.
The text was updated successfully, but these errors were encountered: