Abaabil vs React Bootstrap
Both libraries, measured the same way on the same day: each entry point bundled with its own module graph, gzipped, React treated as external. All twenty-three abaabil components together come to 7,364 B. The same set from React Bootstrap, over the 21 it offers, comes to 34,319 B, or 4.7x the size.
What React Bootstrap is
Bootstrap's markup and behaviour as React components, on top of the Bootstrap stylesheet you load separately.
Per component, gzipped
abaabil's column is its a11y tier, the one most applications should use. 21 components are directly comparable; the widest gap is tooltip at 39x. React Bootstrap has no equivalent for 2 of the twenty-three (combobox, file), so those are left out rather than counted as a win.
| Component | abaabil | React Bootstrap | ratio |
|---|---|---|---|
| button | 557 | 1,589 | 2.9x |
| dialog | 580 | 9,994 | 17x |
| popover | 495 | 17,999 | 36x |
| menu | 1,120 | 16,731 | 15x |
| tooltip | 459 | 18,022 | 39x |
| input | 501 | 2,033 | 4.1x |
| textarea | 506 | 2,033 | 4.0x |
| checkbox | 534 | 2,255 | 4.2x |
| radio | 444 | 2,255 | 5.1x |
| switch | 423 | 2,255 | 5.3x |
| select | 530 | 1,184 | 2.2x |
| slider | 705 | 1,129 | 1.6x |
| accordion | 364 | 6,169 | 17x |
| tabs | 786 | 9,619 | 12x |
| toolbar | 784 | 1,218 | 1.6x |
| breadcrumb | 335 | 2,061 | 6.2x |
| pagination | 689 | 2,243 | 3.3x |
| progress | 493 | 1,505 | 3.1x |
| alert | 341 | 6,626 | 19x |
| avatar | 460 | 1,580 | 3.4x |
| badge | 267 | 1,133 | 4.2x |
| all of them, one bundle | 7,364 | 34,319 | 4.7x |
The last row matters more than any single one above it. A library with a large shared runtime pays for it once, so the gap always narrows as you use more of it. Quoting only the widest row would be the easiest way to mislead you with real numbers.
abaabil's figures are JavaScript only, the same as every other column here, and unlike React Bootstrap it arrives already styled. That cost is real and tracked separately rather than folded in: the whole stylesheet is 5,217 B gzipped if you import all of it. The method, and every library at once, is on the Why page.
When to choose React Bootstrap instead
Your organisation already runs on Bootstrap. Matching an existing design language is a real constraint, and reproducing Bootstrap in something else is a much larger project than accepting its weight.
abaabil is twenty-three components and stops there. It has no date picker, no data grid, no virtualised list, and no plans for any of them. If the thing you need is on that list, the size comparison above is irrelevant to your decision, and you should take the library that has it.
If abaabil is the right fit
Setup is four steps and the first one is npm i abaabil. Every component has its own page with a live example at the tier you would actually import. Or read when not to use it first, which is the section written to talk you out of it.