NebulaKit is a React component library written in TypeScript and styled with precompiled CSS. It ships as two packages, @nebula-kit/core and @nebula-kit-private/pro, built from one source tree. This page lists the technologies behind it and what each one is responsible for.
All components are function components built on hooks and context. The library is developed against React 19 and supports React 18 and 19 in the consuming application. React and React DOM are peer dependencies and are never bundled, so the library always uses the React instance of the host application.
The library is written in TypeScript, and both packages ship their type declarations. Components that let you switch the rendered tag are generic over that tag, so refs and HTML attributes are typed for the element that is actually rendered.
Styles are authored in Sass and compiled at build time into one static stylesheet, shipped in Core and covering Pro too. There is no CSS-in-JS runtime: components describe their appearance through data attributes and CSS custom properties. The stylesheet resolves color, surface, and interaction states from them. Color variations such as hover, active, and divider tones are derived in the browser with the OKLCH relative color syntax.
@floating-ui/react positions every floating surface, such as tooltips and dropdown menus. It handles anchoring to the trigger, flipping and shifting to stay inside the viewport, and limiting the menu height to the available space.
Icons come from lucide-react. Every icon in the library is a Lucide SVG, which inherits the current text color and is sized through the component scale.
The remaining runtime dependencies are small utilities: classnames for class composition, lodash-es imported per function so unused code is tree-shaken, and change-case for string formatting.
Packages are built with tsup on top of esbuild. Each one is published as ES modules only with bundled type declarations, minified and tree-shaken, with React kept external. Pro keeps Core external too and loads it from the installed Core package, so an app runs one copy of the shared code and one provider reaches every component. The stylesheet is compiled separately with the Sass compiler. The documentation site and local development run on Vite.
Vitest with Testing Library runs component and logic specs in a jsdom environment
Playwright component tests render in a real browser to verify computed styles such as themes, brands, and colors
axe-core audits every component in each state that changes its markup (open, selected, disabled, or with an error) and fails on violations such as a missing name or invalid ARIA
ESLint with typescript-eslint and the React and React Hooks plugins enforces code rules and import order. Prettier handles formatting, and madge detects circular imports. A Husky pre-commit hook runs type checking, linting, formatting, and circular import checks on every commit.