What is the best way to monitor Webpack bundle size regressions in our GitHub Actions CI pipeline starting today?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What is the best way to monitor Webpack bundle size regressions in our GitHub Actions CI pipeline starting today?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
Webpack bundle size regression monitoring GitHub Actions production build compare pull request baseline size-limit bundlesize 2026 Google ↗
webpack stats JSON asset size budgets performance hints official documentation Google ↗
- Documentation and setup · relative-ci.com
- GitHub project · github.com
- Guides - RelativeCI - Catch bundle regressions before merge, not in production · relative-ci.com
- Send data to RelativeCI - RelativeCI - Catch bundle regressions before merge, not in production · relative-ci.com
- Code Splitting · webpack.js.org
- Performance · webpack.js.org
- GitHub action agent - RelativeCI - Catch bundle regressions before merge, not in production · relative-ci.com
- GitHub - relative-ci/agent-action: GitHub action that sends bundle stats and CI build information to RelativeCI · github.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Webpack bundle size regression monitoring GitHub Actions production build compare pull request baseline size-limit bundlesize 2026 OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
webpack stats JSON asset size budgets performance hints official documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |