[POC] Experiment with bundle analyzer CLI #71
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an experiment around #123 - opening a PR to brainstorm about the general approach.
The magic is at
packages/bundle-analyzer/src/analyze.ts
, which is used called byexamples/plain-js/package.json
viapnpm run analyze-bundle
.The problem here is that rollup is designed to work with ES modules, so it will always adds a slight transform when looking at CJS. This means the sizes are not fully accurate - but the trends over time (deltas) should be for each of the entrypoints (which are defined by your
package.json
).Example stats:
We need to do some further processing of this stats file to remove entries that you don't care about (aka only focus on entry points).