Repository navigation
chore(Bootstrap): upgrade Bootstrap v6 progress #8739
Replies: 1 comment 2 replies
|
Thanks for raising this, @MaikPeters1511! Short answer: we're following Bootstrap 6 closely, but we haven't started any work on it yet, and we don't plan to until it reaches beta. Bootstrap 6 is currently at 6.0.0-alpha.1 (Oct 8, 2026). The upstream team is explicit that "things can still meaningfully change before beta", that more alphas will ship before the beta/RC stabilization, and that there is no date for a stable release yet. Bootstrap 5 is still supported — we currently ship v5.3.8 — with 5.4.0 planned and no EOL announced, so there's no pressure to migrate right now. For a component library this matters more than for an application: we vendor the CSS/JS and build essentially every component on top of Bootstrap's markup, Sass and JS plugins. The alpha already changes things we rely on everywhere — utility/grid/variant naming moves from infix to prefix (.d-md-none -> .md:d-none, .col-lg-6 -> .lg:col-6, .offcanvas-md -> .md:drawer), Sass moves to @use/@forward with _variables.scss and _maps.scss removed, JS plugins become ESM-only, some components move to native / Details, and CSS layers plus a higher browser floor (Chrome/Edge 130, Firefox 132, Safari 18, no fallbacks) change how our overrides behave. Starting now would likely mean doing that work twice.Our plan:
If you (or anyone else) want to try the alpha in a fork or share notes/spikes here, that's very welcome — we just won't merge anything into the main branch before the API is stable, so nobody's effort gets wasted. I'll update this issue when there's news. Thanks again for the interest! |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
What's the status of Bootstrap 6 in this project?
All reactions