Guidance on axe-core browser bundle size with Storybook/Vite 8
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, storybook, vite
- Domain
- devtools, performance
Research direction
Start by reading related issues #5176 and #5156, then inspect the Storybook accessibility addon's existing dynamic import of axe-core and its browser bundle packaging. The report has no public reproducer, so first establish whether the reported chunk size can be reproduced with a minimal public setup. Done means providing a supported way to budget or reduce bundle size while preserving the complete rules engine and audit semantics.
Written by the indexing model from the issue text.
Description
Is there a supported way to reduce or appropriately budget the size of axe-core when bundled by Storybook's accessibility addon with Vite 8/Rolldown, without disabling or reducing accessibility coverage?
This is a request for guidance, not a claim of a functional bug or demonstrated runtime performance regression.
Environment
- Storybook /
@storybook/react-vite: 10.6.2 @storybook/addon-a11y: 10.6.2axe-core: 4.13.0- Vite: 8.3.3 (Rolldown)
- React: 19.3.0
- Node.js: 24.21.0
Observations
The existing Storybook static build emitted a warning for JavaScript chunks exceeding the default 500 kB threshold.
- Original axe chunk: 573.2 KiB raw / 154.7 KiB gzip.
- Installed
axe.min.js: 580,491 bytes. - Installed
axe.js: 1,305,279 bytes. - The Storybook accessibility addon already uses dynamic
import("axe-core"). - An experimental Rolldown
codeSplitting.groupsconfiguration with a 440 KiB target produced an axe chunk of 586,899 bytes, and the warning remained.
The experimental configuration was reverted. Browser request timing and runtime performance were not measured.
Questions
- Is there a supported smaller or modular browser distribution suitable for Storybook integrations?
- Is there an upstream bundle-size budget or recommended approach for consumers using the complete axe-core rules engine?
- Could future ESM packaging improve bundler optimization without excluding accessibility rules or changing audit semantics?
Related upstream discussions: #5176 (performance budgeting) and #5156 (ESM distribution).
Constraints
We need to preserve full accessibility coverage. We do not want to patch vendored code, depend on external CDNs, or merely increase the chunk-size warning limit.
The measurements originate from a private design-system workspace; a public minimal reproducer is not yet available.
Thank you for guidance on a supported approach.
- Dominant language
- HTML
- Stars
- 7.8k
- Forks
- 998
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dequelabs/axe-core
-
aria-roles: the invalidrole failure message reads as if the role it names is validPossibly taken @gilsonator claimed this 7 days ago. Openfix rule metadata
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
dequelabs/axe-core#5541 · 1 comment ·
Maintainers usually reply within 1 day
-
color-contrast returns elmPartiallyObscured due to subpixel rounding in fullyEncompasses (Firefox/Linux)May be free again @darshpatel1052 claimed this 17 days ago, and no pull request is open. Openungroomed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dequelabs/axe-core#5503 · 1 comment ·
Maintainers usually reply within 1 day
-
docs ungroomed
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
ci
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dequelabs/axe-core#5487 · 2 comments ·
Maintainers usually reply within 1 day
-
Map summary-name to ACT rule 2t702hPossibly taken @KyPython claimed this 34 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
All issues in dequelabs/axe-core
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
-
Pi: paused model calls are reported as "not signed in" when the model's provider comes from an extensionPossibly taken @balcsida claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
microsoft/TokenEconomizer#288 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
NomicFoundation/slang#2391 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
kunchenguid/gh-axi#275 ·
Maintainers usually reply within 1 day
-
sandboxes triage/auto-routed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
docker/sbx-releases#902 ·