Description
I’m using source-map-analyzer in my Angular project to check bundle size. It worked correctly before, showing accurate bundle sizes and a clear breakdown of which packages contributed to them.
Now, the analyzer no longer works as expected:
The web interface shows a much smaller total bundle size than the actual build output.
Every package appears as unmapped, so it’s impossible to see which modules are contributing to the bundle size.
Steps to Reproduce
Install source-map-analyzer in an Angular project.
Build the project and run the explorer.
Observe that the reported bundle size is smaller than the actual size and that dependencies appear unmapped.
Description
I’m using source-map-analyzer in my Angular project to check bundle size. It worked correctly before, showing accurate bundle sizes and a clear breakdown of which packages contributed to them.
Now, the analyzer no longer works as expected:
The web interface shows a much smaller total bundle size than the actual build output.
Every package appears as unmapped, so it’s impossible to see which modules are contributing to the bundle size.
Steps to Reproduce
Install source-map-analyzer in an Angular project.
Build the project and run the explorer.
Observe that the reported bundle size is smaller than the actual size and that dependencies appear unmapped.