<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Cihan Koç</title>
    <description>The latest articles on DEV Community by Cihan Koç (@chnkc41).</description>
    <link>https://dev.to/chnkc41</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3843714%2F4ce63c4d-7f0f-44b8-a425-a0e493f2d383.jpeg</url>
      <title>DEV Community: Cihan Koç</title>
      <link>https://dev.to/chnkc41</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/chnkc41"/>
    <language>en</language>
    <item>
      <title>Catch Invented React Imports with a Small TypeScript Check</title>
      <dc:creator>Cihan Koç</dc:creator>
      <pubDate>Fri, 30 Oct 2026 20:07:48 +0000</pubDate>
      <link>https://dev.to/chnkc41/catch-invented-react-imports-with-a-small-typescript-check-4cc4</link>
      <guid>https://dev.to/chnkc41/catch-invented-react-imports-with-a-small-typescript-check-4cc4</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fw3vsr6k3aj54lw6v0b2j.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fw3vsr6k3aj54lw6v0b2j.png" alt="Trust the types. Check the imports. createPortal maps to react-dom; useState and Fragment map to react." width="800" height="336"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;AI disclosure: OpenAI Codex drafted this tutorial. The examples below were checked by executing TypeScript against the listed installed packages. I maintain Ninna UI; this version uses standard React APIs. The example is a controlled reproduction, not a personal debugging story or a measurement of any agent's error rate.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Cover created with AI-assisted vector code. It maps createPortal to react-dom and useState and Fragment to react.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A generated React feature can contain a familiar API name and still import it from the wrong package. A short TypeScript fixture turns that plausible import into something you can check before accepting the feature.&lt;/p&gt;

&lt;p&gt;The useful technique is to check a few dependency boundaries and prove that the check fails for a known wrong import. A passing command alone is weaker evidence if the fixture was never included in the compilation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with a real export boundary
&lt;/h2&gt;

&lt;p&gt;React's documentation imports &lt;code&gt;createPortal&lt;/code&gt; from &lt;code&gt;react-dom&lt;/code&gt;. This intentionally incorrect fixture imports it from &lt;code&gt;react&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;createPortal&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;react&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;void&lt;/span&gt; &lt;span class="nx"&gt;createPortal&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;With the installed versions used here, TypeScript reports TS2724: the &lt;code&gt;react&lt;/code&gt; module has no exported member named &lt;code&gt;createPortal&lt;/code&gt;. The fix is to use the right public entry point, rather than suppressing the diagnostic or inventing a local module declaration.&lt;/p&gt;

&lt;h2&gt;
  
  
  Create a tiny audit file
&lt;/h2&gt;

&lt;p&gt;In an existing React/TypeScript project, create &lt;code&gt;react-import-audit.ts&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Fragment&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;useState&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;react&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;createPortal&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;react-dom&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;void&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nx"&gt;Fragment&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;useState&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;createPortal&lt;/span&gt;&lt;span class="p"&gt;];&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The file imports and references values but renders nothing. It does not call a Hook outside a component. The goal is just to resolve the exact exports used by a proposed feature.&lt;/p&gt;

&lt;p&gt;If starting with a new project, install the required packages and keep the lockfile:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pnpm add react@latest react-dom@latest
pnpm add &lt;span class="nt"&gt;-D&lt;/span&gt; typescript @types/react @types/react-dom
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Give the check a narrow scope
&lt;/h2&gt;

&lt;p&gt;Create &lt;code&gt;tsconfig.react-audit.json&lt;/code&gt; beside the fixture:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"compilerOptions"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"target"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"ES2022"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"module"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"ESNext"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"moduleResolution"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"bundler"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"lib"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"ES2022"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"DOM"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"DOM.Iterable"&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"types"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"react"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"react-dom"&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"strict"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"skipLibCheck"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"noEmit"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"include"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"react-import-audit.ts"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This configuration checks one fixture without pulling in every application route. &lt;code&gt;bundler&lt;/code&gt; resolution suits this bundled React example; use your framework's supported configuration for the actual app.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pnpm &lt;span class="nb"&gt;exec &lt;/span&gt;tsc &lt;span class="nt"&gt;-p&lt;/span&gt; tsconfig.react-audit.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;First confirm that the correct fixture compiles. Then deliberately move &lt;code&gt;createPortal&lt;/code&gt; into the import from &lt;code&gt;react&lt;/code&gt; and remove its &lt;code&gt;react-dom&lt;/code&gt; import. Confirm TS2724. Restore the correct imports and confirm success again. That failing control helps verify that the command is compiling the intended file.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;noEmit&lt;/code&gt; prevents JavaScript output. &lt;code&gt;skipLibCheck&lt;/code&gt; skips checking declaration-file internals; it does not skip checking the imports in your source fixture. If the error is a missing dependency instead, inspect installation and the working directory before changing compiler options.&lt;/p&gt;

&lt;h2&gt;
  
  
  Make it an acceptance condition
&lt;/h2&gt;

&lt;p&gt;An agent instruction can be small and executable:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Before changing a React import:
1. Check the installed package's public exports and current docs.
2. Keep a small fixture for the APIs the feature needs.
3. Prove the fixture catches one known wrong package export.
4. Run the app's normal typecheck and production build.
Do not silence an export error with any, @ts-ignore,
or a fabricated module declaration.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What this result means
&lt;/h2&gt;

&lt;p&gt;The recorded check uses React and React DOM 19.2.8 with TypeScript 5.9.3. The correct fixture produced no diagnostics; the deliberately wrong import produced TS2724. Rerun it after dependency upgrades instead of assuming an old example describes the installed packages.&lt;/p&gt;

&lt;p&gt;This checks an import boundary. It does not render a portal, verify the target DOM node, check event propagation, measure a bundle, or establish accessibility. A real feature still needs its normal typecheck, build, runtime tests and interaction checks. Passing declarations also cannot prove that runtime code perfectly matches its published types.&lt;/p&gt;

&lt;p&gt;Start with the APIs the feature actually uses. Keep the fixture small, prove it can fail, and keep broader application checks in the acceptance criteria.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://react.dev/reference/react-dom/createPortal" rel="noopener noreferrer"&gt;React: createPortal&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.typescriptlang.org/tsconfig/moduleResolution" rel="noopener noreferrer"&gt;TypeScript: moduleResolution&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.typescriptlang.org/tsconfig/noEmit" rel="noopener noreferrer"&gt;TypeScript: noEmit&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.typescriptlang.org/tsconfig/skipLibCheck" rel="noopener noreferrer"&gt;TypeScript: skipLibCheck&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>react</category>
      <category>typescript</category>
      <category>webdev</category>
      <category>ai</category>
    </item>
    <item>
      <title>Why I Built ASOShot: A Free App Store Screenshot Editor</title>
      <dc:creator>Cihan Koç</dc:creator>
      <pubDate>Sun, 20 Sep 2026 19:50:57 +0000</pubDate>
      <link>https://dev.to/chnkc41/why-i-built-asoshot-a-free-app-store-screenshot-editor-5apf</link>
      <guid>https://dev.to/chnkc41/why-i-built-asoshot-a-free-app-store-screenshot-editor-5apf</guid>
      <description>&lt;p&gt;Preparing store screenshots should be a short release task. In practice, it often turns into a small design project: find the current export sizes, place several captures in consistent frames, keep text readable, repeat the work for every locale, and discover a dimension error only after uploading.&lt;/p&gt;

&lt;p&gt;I built &lt;a href="https://asoshot.com" rel="noopener noreferrer"&gt;ASOShot&lt;/a&gt; to make that workflow less fragile. It is a free browser-based editor for App Store and Google Play screenshot graphics. You can start from a template, add real app captures, edit captions, switch between flat and perspective device frames, and export full-resolution images without creating an account.&lt;/p&gt;

&lt;p&gt;This is not an independent review. I am the maker, and this is the reasoning behind the product.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem was repetition, not a lack of design tools
&lt;/h2&gt;

&lt;p&gt;General-purpose design software can produce excellent store assets. The difficulty is maintaining a matrix of screens, store sizes, and languages without introducing drift.&lt;/p&gt;

&lt;p&gt;A screenshot set has two kinds of decisions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Shared decisions: background, typography, device model, frame color, and the overall composition.&lt;/li&gt;
&lt;li&gt;Exceptions: a longer German headline, a different crop on one screen, or a frame shifted to reveal an important control.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Copying artboards handles the first version. It becomes harder when a later change should reach every screen except the few intentional overrides.&lt;/p&gt;

&lt;p&gt;ASOShot models that split directly. The Global Studio controls shared settings. A per-screen panel stores only the properties changed for that screen. If one frame has a custom rotation, it can still inherit a later global color or shadow change.&lt;/p&gt;

&lt;h2&gt;
  
  
  The editor is local-first
&lt;/h2&gt;

&lt;p&gt;Imported screenshots and canvas rendering stay in the browser. Projects can be saved in browser storage or downloaded as a portable JSON backup. Translation is the exception: when used, only caption text and the selected languages are sent to the configured translation endpoint. Images are not sent for translation.&lt;/p&gt;

&lt;p&gt;That boundary matters for unreleased apps. It also keeps the basic workflow simple: open the editor, choose a template, and start working.&lt;/p&gt;

&lt;h2&gt;
  
  
  Export fidelity became the main engineering constraint
&lt;/h2&gt;

&lt;p&gt;The first renderer used a DOM-to-image approach. It worked for ordinary layout but failed on realistic perspective frames. Browsers composite CSS 3D layers for the current display size; enlarging that result for a store-resolution export can expose blurred edges and a mismatch between the preview and the downloaded file.&lt;/p&gt;

&lt;p&gt;The current export path draws directly to a 2D canvas. Backgrounds, captions, badges, shadows, device edges, and screen images use the same geometry as the preview. Perspective devices are projected and drawn in slices instead of capturing the editor DOM.&lt;/p&gt;

&lt;p&gt;The preview remains fluid, while export runs at the target's native pixel dimensions. That separation lets a small editor preview stay responsive without making it the source bitmap for the final image.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is included today
&lt;/h2&gt;

&lt;p&gt;The current project includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;15 category templates&lt;/li&gt;
&lt;li&gt;iPhone, iPad, and Android export targets&lt;/li&gt;
&lt;li&gt;Flat and perspective device frames&lt;/li&gt;
&lt;li&gt;Multiple frames per screen, including cross-screen layouts&lt;/li&gt;
&lt;li&gt;Captions for more than 20 locale presets&lt;/li&gt;
&lt;li&gt;Full-resolution PNG and JPEG export&lt;/li&gt;
&lt;li&gt;Batch ZIP export across selected screens, sizes, and locales&lt;/li&gt;
&lt;li&gt;JSON project backup and restore&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There is no public screenshot-generation API or MCP server. ASOShot is currently an interactive browser editor. I prefer stating that plainly rather than advertising a roadmap item as a finished feature.&lt;/p&gt;

&lt;h2&gt;
  
  
  The workflow I wanted
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Pick a template close to the app's visual category.&lt;/li&gt;
&lt;li&gt;Select the store sizes that will actually be submitted.&lt;/li&gt;
&lt;li&gt;Upload real product captures.&lt;/li&gt;
&lt;li&gt;Write one clear benefit per screen.&lt;/li&gt;
&lt;li&gt;Review frame placement and text at every selected size.&lt;/li&gt;
&lt;li&gt;Add locales, then review automatic translations before publishing.&lt;/li&gt;
&lt;li&gt;Export the final matrix as a ZIP.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Apple and Google change asset requirements, so the editor is not a substitute for checking their current documentation before a release. It is meant to remove the repetitive composition and export work after those targets are known.&lt;/p&gt;

&lt;p&gt;ASOShot is available at &lt;a href="https://asoshot.com" rel="noopener noreferrer"&gt;asoshot.com&lt;/a&gt;. If you try it on a real release, the most useful feedback is specific: which screen size, frame arrangement, or localization step slowed you down?&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>webdev</category>
      <category>mobile</category>
      <category>aso</category>
    </item>
    <item>
      <title>5 Awesome (FREE) React UI Libraries to Use in 2026</title>
      <dc:creator>Cihan Koç</dc:creator>
      <pubDate>Sat, 29 Aug 2026 22:17:07 +0000</pubDate>
      <link>https://dev.to/chnkc41/5-awesome-free-react-ui-libraries-to-use-in-2026-3g83</link>
      <guid>https://dev.to/chnkc41/5-awesome-free-react-ui-libraries-to-use-in-2026-3g83</guid>
      <description>&lt;p&gt;You don't need to spend $299 on a premium UI kit to build a production-quality React application. The open-source React ecosystem in 2026 offers component libraries that rival - and often surpass - commercial alternatives.&lt;/p&gt;

&lt;p&gt;Here are 5 free, MIT-licensed React UI libraries that are actually worth building on. No trial periods. No feature gates. No "contact sales for pricing."&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Ninna UI - Zero-Cost, Zero-Runtime
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;License:&lt;/strong&gt; MIT · &lt;strong&gt;Cost:&lt;/strong&gt; $0 forever · &lt;strong&gt;Components:&lt;/strong&gt; 69&lt;/p&gt;

&lt;p&gt;Ninna UI is the newest library on this list, but it was designed with every lesson learned from the last decade of React UI development. The core insight: &lt;strong&gt;your design system should be CSS, not JavaScript&lt;/strong&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  What $0 gets you
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;69 production-ready components&lt;/strong&gt; - buttons, forms, modals, tables, navigation, data display&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;12 tree-shakeable packages&lt;/strong&gt; - &lt;code&gt;@ninna-ui/primitives&lt;/code&gt;, &lt;code&gt;@ninna-ui/forms&lt;/code&gt;, &lt;code&gt;@ninna-ui/overlays&lt;/code&gt;, etc.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;5 theme presets&lt;/strong&gt; - Default (purple), Ocean (blue), Sunset (orange), Forest (green), Minimal (mono)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;WCAG 2.1 AA accessibility&lt;/strong&gt; - Radix UI internals for complex widgets&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;oklch perceptual colors&lt;/strong&gt; - guaranteed contrast ratios in every theme&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;700+ automated tests&lt;/strong&gt; - vitest + vitest-axe covering every component&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CLI scaffolding&lt;/strong&gt; - &lt;code&gt;npx @ninna-ui/cli init my-app&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The magic trick
&lt;/h3&gt;

&lt;p&gt;Two lines of CSS replace what other libraries need 50 lines of JavaScript to achieve:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="k"&gt;@import&lt;/span&gt; &lt;span class="s1"&gt;"tailwindcss"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;@import&lt;/span&gt; &lt;span class="s1"&gt;"@ninna-ui/core/theme/presets/default.css"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;No &lt;code&gt;ThemeProvider&lt;/code&gt;. No &lt;code&gt;ChakraProvider&lt;/code&gt;. No &lt;code&gt;createTheme()&lt;/code&gt;. No &lt;code&gt;ConfigProvider&lt;/code&gt;. Just CSS. Your app hydrates faster because there's zero JavaScript theming overhead.&lt;/p&gt;

&lt;h3&gt;
  
  
  Code example
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Button&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;Heading&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;Badge&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@ninna-ui/primitives&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Input&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;Field&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;Select&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@ninna-ui/forms&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Modal&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@ninna-ui/overlays&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;VStack&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@ninna-ui/layout&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Alert&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@ninna-ui/feedback&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;SignupForm&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;VStack&lt;/span&gt; &lt;span class="na"&gt;gap&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"6"&lt;/span&gt; &lt;span class="na"&gt;className&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"max-w-md mx-auto p-8"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Heading&lt;/span&gt; &lt;span class="na"&gt;as&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"h1"&lt;/span&gt; &lt;span class="na"&gt;size&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"3xl"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;Create Account&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Heading&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;

      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Field&lt;/span&gt; &lt;span class="na"&gt;label&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"Email"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
        &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Input&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"email"&lt;/span&gt; &lt;span class="na"&gt;placeholder&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"you@example.com"&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Field&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;

      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Field&lt;/span&gt; &lt;span class="na"&gt;label&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"Role"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
        &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Select&lt;/span&gt;
          &lt;span class="na"&gt;options&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;
            &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;value&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;developer&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;label&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Developer&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
            &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;value&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;designer&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;label&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Designer&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
            &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;value&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;manager&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;label&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Manager&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
          &lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
        &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Field&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;

      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Button&lt;/span&gt; &lt;span class="na"&gt;color&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"primary"&lt;/span&gt; &lt;span class="na"&gt;className&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"w-full"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
        Sign Up Free
      &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Button&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;

      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Alert&lt;/span&gt; &lt;span class="na"&gt;color&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"info"&lt;/span&gt; &lt;span class="na"&gt;variant&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"soft"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
        All 69 components are free and MIT-licensed.
      &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Alert&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;VStack&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;→ &lt;a href="https://ninna-ui.dev/getting-started/installation" rel="noopener noreferrer"&gt;Get started&lt;/a&gt; · &lt;a href="https://ninna-ui.dev/examples" rel="noopener noreferrer"&gt;Examples&lt;/a&gt; · &lt;a href="https://github.com/ninna-ui/ninna-ui" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  2. Mantine - The Kitchen Sink
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;License:&lt;/strong&gt; MIT · &lt;strong&gt;Cost:&lt;/strong&gt; $0 forever · &lt;strong&gt;Components:&lt;/strong&gt; 120+&lt;/p&gt;

&lt;p&gt;Mantine v7 provides the largest collection of free React components and hooks. It goes beyond UI with built-in form management, notifications, rich text editing, date pickers, and more.&lt;/p&gt;

&lt;h3&gt;
  
  
  What $0 gets you
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;120+ components and 70+ hooks&lt;/li&gt;
&lt;li&gt;Built-in form library with validation&lt;/li&gt;
&lt;li&gt;Date picker components (no separate package needed)&lt;/li&gt;
&lt;li&gt;Rich text editor (Tiptap-based)&lt;/li&gt;
&lt;li&gt;Notification system&lt;/li&gt;
&lt;li&gt;Spotlight search component&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The trade-off
&lt;/h3&gt;

&lt;p&gt;Mantine uses its own styling system (CSS modules / PostCSS) - it's not Tailwind CSS native. If your team is all-in on Tailwind, you'll be mixing two styling approaches. The &lt;code&gt;MantineProvider&lt;/code&gt; wrapper adds JavaScript runtime overhead.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Button&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;TextInput&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@mantine/core&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;useForm&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@mantine/form&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;LoginForm&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;form&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;useForm&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
    &lt;span class="na"&gt;initialValues&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;email&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;""&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;password&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;""&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="p"&gt;});&lt;/span&gt;

  &lt;span class="k"&gt;return &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;form&lt;/span&gt; &lt;span class="na"&gt;onSubmit&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nx"&gt;form&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;onSubmit&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;handleSubmit&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;TextInput&lt;/span&gt; &lt;span class="na"&gt;label&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"Email"&lt;/span&gt; &lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="p"&gt;...&lt;/span&gt;&lt;span class="nx"&gt;form&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;getInputProps&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;email&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Button&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"submit"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;Login&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Button&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;form&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;→ &lt;a href="https://mantine.dev" rel="noopener noreferrer"&gt;mantine.dev&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  3. Chakra UI - The DX Champion
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;License:&lt;/strong&gt; MIT · &lt;strong&gt;Cost:&lt;/strong&gt; $0 forever · &lt;strong&gt;Components:&lt;/strong&gt; 100+&lt;/p&gt;

&lt;p&gt;Chakra UI v3, rebuilt on Ark UI and Panda CSS, maintains its reputation for excellent developer experience. The prop-based API is intuitive, TypeScript support is strong, and the component set covers most needs.&lt;/p&gt;

&lt;h3&gt;
  
  
  What $0 gets you
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;100+ well-designed components&lt;/li&gt;
&lt;li&gt;Rebuilt on Ark UI state machines (v3)&lt;/li&gt;
&lt;li&gt;Strong TypeScript support&lt;/li&gt;
&lt;li&gt;Excellent documentation&lt;/li&gt;
&lt;li&gt;Active Discord community&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The trade-off
&lt;/h3&gt;

&lt;p&gt;Chakra v3 moved from Emotion to Panda CSS, which introduces a build step and a learning curve for teams not familiar with Panda's token system. &lt;code&gt;ChakraProvider&lt;/code&gt; and &lt;code&gt;ColorModeProvider&lt;/code&gt; are still required.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Button&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;Input&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;Stack&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@chakra-ui/react&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;ContactForm&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Stack&lt;/span&gt; &lt;span class="na"&gt;gap&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"4"&lt;/span&gt; &lt;span class="na"&gt;maxW&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"md"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Input&lt;/span&gt; &lt;span class="na"&gt;placeholder&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"Your email"&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Button&lt;/span&gt; &lt;span class="na"&gt;colorPalette&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"blue"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;Send Message&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Button&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Stack&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;→ &lt;a href="https://chakra-ui.com" rel="noopener noreferrer"&gt;chakra-ui.com&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  4. shadcn/ui - Own Your Components
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;License:&lt;/strong&gt; MIT · &lt;strong&gt;Cost:&lt;/strong&gt; $0 forever · &lt;strong&gt;Components:&lt;/strong&gt; 40+&lt;/p&gt;

&lt;p&gt;shadcn/ui isn't a traditional library - it's a CLI that copies Radix + Tailwind component source code into your project. You get full ownership and customization freedom.&lt;/p&gt;

&lt;h3&gt;
  
  
  What $0 gets you
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;40+ copy-paste components&lt;/li&gt;
&lt;li&gt;Radix UI accessibility&lt;/li&gt;
&lt;li&gt;Tailwind CSS styling&lt;/li&gt;
&lt;li&gt;Full code ownership&lt;/li&gt;
&lt;li&gt;Massive community&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The trade-off
&lt;/h3&gt;

&lt;p&gt;You maintain every component yourself. No &lt;code&gt;npm update&lt;/code&gt;. When shadcn fixes a bug upstream, you manually re-copy or patch. Managing Radix peer dependencies across components adds complexity. Cross-project consistency is challenging since each project gets a unique fork.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="c1"&gt;// After copying the component into your project:&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Button&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@/components/ui/button&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Input&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@/components/ui/input&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Button&lt;/span&gt; &lt;span class="na"&gt;variant&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"outline"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;Cancel&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Button&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Input&lt;/span&gt; &lt;span class="na"&gt;placeholder&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"Search..."&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;→ &lt;a href="https://ui.shadcn.com" rel="noopener noreferrer"&gt;ui.shadcn.com&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  5. Radix UI - The Headless Foundation
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;License:&lt;/strong&gt; MIT · &lt;strong&gt;Cost:&lt;/strong&gt; $0 forever · &lt;strong&gt;Components:&lt;/strong&gt; 30+ primitives&lt;/p&gt;

&lt;p&gt;Radix UI provides unstyled, accessible React primitives. It's the accessibility engine behind shadcn/ui and Ninna UI, and it's excellent when you need complete control over visual design.&lt;/p&gt;

&lt;h3&gt;
  
  
  What $0 gets you
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;30+ headless primitives with best-in-class accessibility&lt;/li&gt;
&lt;li&gt;WAI-ARIA compliance out of the box&lt;/li&gt;
&lt;li&gt;Keyboard navigation, focus management, screen reader support&lt;/li&gt;
&lt;li&gt;Works with any CSS approach (Tailwind, CSS modules, styled-components)&lt;/li&gt;
&lt;li&gt;Radix Themes (optional styled layer)&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The trade-off
&lt;/h3&gt;

&lt;p&gt;You must style everything from scratch. Building a complete design system on raw Radix primitives is weeks of work. There's no theming, no color system, no layout components - just behavior and accessibility.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="nx"&gt;Dialog&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@radix-ui/react-dialog&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Dialog&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Root&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Dialog&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Trigger&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;Open&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Dialog&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Trigger&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Dialog&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Portal&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Dialog&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Overlay&lt;/span&gt; &lt;span class="na"&gt;className&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"fixed inset-0 bg-black/50"&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Dialog&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Content&lt;/span&gt; &lt;span class="na"&gt;className&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"fixed top-1/2 left-1/2 -translate-x-1/2 -translate-y-1/2 bg-white rounded-lg p-6"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Dialog&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Title&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;Edit Profile&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Dialog&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Title&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="cm"&gt;/* You style everything */&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Dialog&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Content&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Dialog&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Portal&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Dialog&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;Root&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;→ &lt;a href="https://www.radix-ui.com" rel="noopener noreferrer"&gt;radix-ui.com&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Quick Decision Matrix
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Priority&lt;/th&gt;
&lt;th&gt;Best Choice&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Tailwind v4 + a11y + zero runtime&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Ninna UI&lt;/td&gt;
&lt;td&gt;CSS-only theming, Radix internals, React 19 native&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Maximum features&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Mantine&lt;/td&gt;
&lt;td&gt;120+ components, forms, dates, notifications built in&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Best prop API / DX&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Chakra UI&lt;/td&gt;
&lt;td&gt;Intuitive API, strong TS, excellent docs&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Full code ownership&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;shadcn/ui&lt;/td&gt;
&lt;td&gt;Copy-paste model, customize anything&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Just the accessibility layer&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Radix UI&lt;/td&gt;
&lt;td&gt;Best-in-class headless primitives&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  The Cost of "Free"
&lt;/h2&gt;

&lt;p&gt;Every library on this list is genuinely free - MIT-licensed, no feature gates, no upsells. But "free" doesn't mean "zero cost." The real cost is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Learning time&lt;/strong&gt; - how quickly can your team be productive?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bundle size&lt;/strong&gt; - does the library add significant JavaScript overhead?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Maintenance&lt;/strong&gt; - how much work is keeping dependencies updated?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Accessibility debt&lt;/strong&gt; - does the library solve a11y, or leave it to you?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Migration cost&lt;/strong&gt; - if you outgrow the library, how hard is it to switch?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ninna UI was designed to minimize all five of these costs. CSS-only theming means smaller bundles and simpler mental model. npm packages mean standard updates. Radix internals mean accessibility is solved. And 98 data-slot CSS targets mean you can customize anything without forking.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx @ninna-ui/cli init my-app
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;→ &lt;a href="https://ninna-ui.dev/getting-started/installation" rel="noopener noreferrer"&gt;Documentation&lt;/a&gt;&lt;br&gt;
→ &lt;a href="https://ninna-ui.dev/examples" rel="noopener noreferrer"&gt;Live examples&lt;/a&gt;&lt;/p&gt;




</description>
      <category>react</category>
      <category>opensource</category>
      <category>webdev</category>
      <category>frontend</category>
    </item>
    <item>
      <title>Copy-Paste Components vs npm Packages: shadcn/ui vs Ninna UI in 2026</title>
      <dc:creator>Cihan Koç</dc:creator>
      <pubDate>Wed, 01 Apr 2026 19:47:48 +0000</pubDate>
      <link>https://dev.to/chnkc41/copy-paste-components-vs-npm-packages-shadcnui-vs-ninna-ui-in-2026-1n0a</link>
      <guid>https://dev.to/chnkc41/copy-paste-components-vs-npm-packages-shadcnui-vs-ninna-ui-in-2026-1n0a</guid>
      <description>&lt;p&gt;The React component library debate used to be straightforward: pick an npm package, install it, use it. Then shadcn/ui arrived and proposed something radical: &lt;strong&gt;don't install components - copy them into your codebase&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Two years later, both approaches have proven themselves in production. This article is an honest comparison of the copy-paste model (shadcn/ui) and the npm package model (Ninna UI) - examining the trade-offs that matter at scale.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Two Models
&lt;/h2&gt;

&lt;h3&gt;
  
  
  shadcn/ui: Copy-Paste
&lt;/h3&gt;

&lt;p&gt;You run a CLI command that copies React component source files directly into your project. The components use Radix UI primitives and Tailwind CSS for styling. You own every line of code.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx shadcn@latest add button dialog &lt;span class="k"&gt;select&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This creates files in your &lt;code&gt;components/ui/&lt;/code&gt; directory. They're yours. Modify them freely.&lt;/p&gt;

&lt;h3&gt;
  
  
  Ninna UI: npm Packages
&lt;/h3&gt;

&lt;p&gt;You install packages from npm. Components are consumed as imports. You customize via CSS custom properties, Tailwind utilities, and &lt;code&gt;data-slot&lt;/code&gt; CSS selectors - without modifying source code.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pnpm add @ninna-ui/primitives @ninna-ui/overlays @ninna-ui/forms
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Button&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@ninna-ui/primitives&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Modal&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@ninna-ui/overlays&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Select&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@ninna-ui/forms&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  The Trade-Offs
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Updates and Maintenance
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;shadcn/ui:&lt;/strong&gt;&lt;br&gt;
When a bug is fixed upstream, you have two options:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Re-copy the component (losing your customizations)&lt;/li&gt;
&lt;li&gt;Manually apply the patch to your local copy&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There's no &lt;code&gt;npm update&lt;/code&gt;. No changelog. No semantic versioning. Each project has a unique fork that diverges from upstream over time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ninna UI:&lt;/strong&gt;&lt;br&gt;
Standard npm workflow. &lt;code&gt;pnpm update @ninna-ui/primitives&lt;/code&gt; gets you bug fixes, accessibility improvements, and new features - while preserving your customizations (which live in CSS, not in component source).&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pnpm update @ninna-ui/primitives
&lt;span class="c"&gt;# Changelog at https://ninna-ui.dev/changelog&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Verdict:&lt;/strong&gt; npm packages win for teams that value maintenance predictability. Copy-paste wins for developers who rarely need upstream updates.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Customization Depth
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;shadcn/ui:&lt;/strong&gt;&lt;br&gt;
You own the code. You can change anything - the component structure, the HTML output, the ARIA behavior, the prop API. There's no abstraction between you and the implementation.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="c1"&gt;// You can literally rewrite the component&lt;/span&gt;
&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;Button&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="nx"&gt;className&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;...&lt;/span&gt;&lt;span class="nx"&gt;props&lt;/span&gt; &lt;span class="p"&gt;})&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;button&lt;/span&gt;
      &lt;span class="na"&gt;className&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nf"&gt;cn&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;my-completely-custom-button-styles&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;className&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
      &lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="p"&gt;...&lt;/span&gt;&lt;span class="nx"&gt;props&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
    &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Ninna UI:&lt;/strong&gt;&lt;br&gt;
You customize via 3 layers without touching source code:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Tailwind utilities&lt;/strong&gt; - &lt;code&gt;className&lt;/code&gt; prop on every component&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CSS custom properties&lt;/strong&gt; - theme tokens (&lt;code&gt;--color-primary&lt;/code&gt;, &lt;code&gt;--radius-lg&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;data-slot selectors&lt;/strong&gt; - target any internal element
&lt;/li&gt;
&lt;/ol&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="c"&gt;/* Customize any internal element via CSS */&lt;/span&gt;
&lt;span class="o"&gt;[&lt;/span&gt;&lt;span class="nt"&gt;data-slot&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s1"&gt;"trigger"&lt;/span&gt;&lt;span class="o"&gt;]&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;border-radius&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;var&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;--radius-full&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="nl"&gt;font-weight&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="m"&gt;600&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="o"&gt;[&lt;/span&gt;&lt;span class="nt"&gt;data-slot&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s1"&gt;"content"&lt;/span&gt;&lt;span class="o"&gt;]&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;animation&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;slide-down&lt;/span&gt; &lt;span class="m"&gt;200ms&lt;/span&gt; &lt;span class="n"&gt;ease-out&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;98 data-slot targets cover every customizable element across all 69 components - without forking a single file.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Verdict:&lt;/strong&gt; shadcn/ui wins for unlimited structural changes. Ninna UI wins for styling customization without the maintenance cost of owning source code.&lt;/p&gt;
&lt;h3&gt;
  
  
  3. Cross-Project Consistency
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;shadcn/ui:&lt;/strong&gt;&lt;br&gt;
Each project gets a unique copy of every component. Over time, these diverge. A &lt;code&gt;Button&lt;/code&gt; in Project A is different from &lt;code&gt;Button&lt;/code&gt; in Project B. Keeping them synchronized requires manual discipline or a private component library (which is... an npm package).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ninna UI:&lt;/strong&gt;&lt;br&gt;
Every project uses the same &lt;code&gt;@ninna-ui/primitives&lt;/code&gt; version. Same API, same accessibility, same behavior. Different visual styles via CSS theme presets - but the component contracts are identical.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="c"&gt;/* Project A: Default theme */&lt;/span&gt;
&lt;span class="k"&gt;@import&lt;/span&gt; &lt;span class="s1"&gt;"@ninna-ui/core/theme/presets/default.css"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="c"&gt;/* Project B: Ocean theme */&lt;/span&gt;
&lt;span class="k"&gt;@import&lt;/span&gt; &lt;span class="s1"&gt;"@ninna-ui/core/theme/presets/ocean.css"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="c"&gt;/* Same components, different look */&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Verdict:&lt;/strong&gt; npm packages win decisively for multi-project teams and agencies.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Dependency Management
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;shadcn/ui:&lt;/strong&gt;&lt;br&gt;
Each copied component may depend on specific Radix UI packages. A typical shadcn/ui project accumulates 10-15+ Radix packages:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"@radix-ui/react-dialog"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"^1.x"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"@radix-ui/react-dropdown-menu"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"^2.x"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"@radix-ui/react-select"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"^2.x"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"@radix-ui/react-tooltip"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"^1.x"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"@radix-ui/react-popover"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"^1.x"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"@radix-ui/react-accordion"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"^1.x"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"class-variance-authority"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"^0.7"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"cmdk"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"^1.x"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"lucide-react"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"^0.x"&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="err"&gt;//&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;...&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;more&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;for&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;each&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="err"&gt;component&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You manage version compatibility yourself. When Radix releases a breaking change, you update each component individually.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ninna UI:&lt;/strong&gt;&lt;br&gt;
Radix is an internal implementation detail. You never import it. You never manage its versions. Ninna UI wraps 11 Radix primitives behind clean interfaces:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"@ninna-ui/primitives"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"^0.4.1"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"@ninna-ui/overlays"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"^0.4.1"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"@ninna-ui/forms"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"^0.4.1"&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three dependencies instead of fifteen. Radix version management is Ninna UI's responsibility, not yours.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Verdict:&lt;/strong&gt; npm packages win for dependency hygiene. Copy-paste forces you to be a Radix version manager.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Bundle Size
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;shadcn/ui:&lt;/strong&gt;&lt;br&gt;
You only include the components you use, and since they're local files, tree-shaking is perfect. No unused code reaches the bundle.&lt;/p&gt;

&lt;p&gt;However, each component pulls its own Radix dependency, and multiple components may include overlapping utility code (cn(), cva(), etc.).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ninna UI:&lt;/strong&gt;&lt;br&gt;
12 tree-shakeable ESM packages with &lt;code&gt;sideEffects: false&lt;/code&gt;. Import only what you use - unused components are eliminated by your bundler.&lt;/p&gt;

&lt;p&gt;The theming layer is pure CSS (zero JavaScript), which means your theming overhead is literally 0 KB of JavaScript. shadcn/ui's theming is also CSS-based, so this is roughly equivalent.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Verdict:&lt;/strong&gt; Roughly equal. Both approaches tree-shake well. Ninna UI has a slight edge because Radix dependencies are deduplicated internally.&lt;/p&gt;
&lt;h3&gt;
  
  
  6. TypeScript Experience
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;shadcn/ui:&lt;/strong&gt;&lt;br&gt;
Types depend on how well you maintain the copied code. Out of the box, components use &lt;code&gt;cva&lt;/code&gt; for variant typing, which provides basic prop safety. But types can degrade as you modify components.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ninna UI:&lt;/strong&gt;&lt;br&gt;
Full TypeScript generics on every component, maintained by the library team. Generic &lt;code&gt;Select&amp;lt;T&amp;gt;&lt;/code&gt;, discriminated union props, strict event handlers:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="kd"&gt;type&lt;/span&gt; &lt;span class="nx"&gt;Role&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;admin&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;editor&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;viewer&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Select&lt;/span&gt;&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nx"&gt;Role&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="nx"&gt;options&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;{[&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;value&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;admin&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;label&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Admin&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;value&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;editor&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;label&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Editor&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="p"&gt;]}&lt;/span&gt;
  &lt;span class="nx"&gt;onChange&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;{(&lt;/span&gt;&lt;span class="nx"&gt;role&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="c1"&gt;// role is typed as Role, not string&lt;/span&gt;
  &lt;span class="p"&gt;}}&lt;/span&gt;
&lt;span class="sr"&gt;/&lt;/span&gt;&lt;span class="err"&gt;&amp;gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Verdict:&lt;/strong&gt; Ninna UI wins for type depth and consistency. shadcn/ui types are "good enough" but degrade with customization.&lt;/p&gt;

&lt;h3&gt;
  
  
  7. Accessibility
&lt;/h3&gt;

&lt;p&gt;Both use Radix UI primitives, so the accessibility foundation is identical. The difference is maintenance:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;shadcn/ui:&lt;/strong&gt; When Radix improves accessibility (new ARIA patterns, better screen reader support), you must manually update your copied components to benefit.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ninna UI:&lt;/strong&gt; Accessibility improvements ship via &lt;code&gt;npm update&lt;/code&gt;. You get them automatically.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Verdict:&lt;/strong&gt; Equivalent at install time. Ninna UI wins over time because updates are automatic.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision Framework
&lt;/h2&gt;

&lt;p&gt;Choose &lt;strong&gt;shadcn/ui&lt;/strong&gt; if:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You're a solo developer or small team&lt;/li&gt;
&lt;li&gt;You want unlimited structural control over components&lt;/li&gt;
&lt;li&gt;You rarely need upstream updates&lt;/li&gt;
&lt;li&gt;You're comfortable managing Radix dependencies&lt;/li&gt;
&lt;li&gt;You enjoy customizing component internals&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Choose &lt;strong&gt;Ninna UI&lt;/strong&gt; if:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You work across multiple projects&lt;/li&gt;
&lt;li&gt;You want standard npm maintenance (&lt;code&gt;update&lt;/code&gt;, &lt;code&gt;audit&lt;/code&gt;, semver)&lt;/li&gt;
&lt;li&gt;You prefer CSS customization over source code modification&lt;/li&gt;
&lt;li&gt;You want Radix accessibility without managing Radix directly&lt;/li&gt;
&lt;li&gt;You need consistent component behavior across your organization&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Choose &lt;strong&gt;both&lt;/strong&gt; if:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You want the npm package model for most components&lt;/li&gt;
&lt;li&gt;But need to fork specific components for edge cases&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ninna UI's &lt;code&gt;data-slot&lt;/code&gt; CSS API means you'll rarely need to fork. But when you do, nothing stops you from copying one component's source and customizing it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Bigger Picture
&lt;/h2&gt;

&lt;p&gt;The copy-paste vs npm debate isn't really about shadcn/ui vs Ninna UI. It's about two different philosophies:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Copy-paste says:&lt;/strong&gt; "Libraries are constraints. Own your code."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;npm packages say:&lt;/strong&gt; "Libraries are leverage. Own your product."&lt;/p&gt;

&lt;p&gt;Both are valid. But the npm model has 20 years of proven infrastructure - semantic versioning, changelogs, automated updates, dependency auditing, security patches - that the copy-paste model intentionally abandons.&lt;/p&gt;

&lt;p&gt;In 2026, with React Server Components, Tailwind CSS v4, and the increasing complexity of web accessibility requirements, the case for professional-grade npm packages has never been stronger.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try Ninna UI
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx @ninna-ui/cli init my-app
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;→ &lt;a href="https://ninna-ui.dev/getting-started/installation" rel="noopener noreferrer"&gt;Documentation&lt;/a&gt;&lt;br&gt;
→ &lt;a href="https://ninna-ui.dev/compare/shadcn-vs-ninna-ui" rel="noopener noreferrer"&gt;shadcn/ui vs Ninna UI comparison&lt;/a&gt;&lt;br&gt;
→ &lt;a href="https://ninna-ui.dev/compare" rel="noopener noreferrer"&gt;All library comparisons&lt;/a&gt;&lt;/p&gt;

</description>
      <category>frontend</category>
      <category>npm</category>
      <category>react</category>
      <category>ui</category>
    </item>
    <item>
      <title>TailwindCSS Libraries You Should Know and Use in 2026</title>
      <dc:creator>Cihan Koç</dc:creator>
      <pubDate>Fri, 27 Mar 2026 15:51:49 +0000</pubDate>
      <link>https://dev.to/chnkc41/tailwindcss-libraries-you-should-know-and-use-in-2026-42e</link>
      <guid>https://dev.to/chnkc41/tailwindcss-libraries-you-should-know-and-use-in-2026-42e</guid>
      <description>&lt;p&gt;Tailwind CSS v4 didn't just improve the framework - it reshaped the entire ecosystem around it. The move to CSS-first configuration, the Lightning CSS engine, and native oklch color support have made some libraries more relevant and others obsolete.&lt;/p&gt;

&lt;p&gt;This isn't another "top 10 UI kits" list. This is a curated guide to the &lt;strong&gt;libraries, plugins, and tools&lt;/strong&gt; that make Tailwind CSS v4 development genuinely faster and better in 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  Component Libraries
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Ninna UI - The CSS-First React Library
&lt;/h3&gt;

&lt;p&gt;If you're building with React 19 and Tailwind CSS v4, Ninna UI is the library that was built for this exact stack. 69 accessible components, zero-runtime theming, oklch colors, and a setup that takes literally two lines of CSS.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="k"&gt;@import&lt;/span&gt; &lt;span class="s1"&gt;"tailwindcss"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;@import&lt;/span&gt; &lt;span class="s1"&gt;"@ninna-ui/core/theme/presets/default.css"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;What makes it different from every other React component library: &lt;strong&gt;no ThemeProvider&lt;/strong&gt;. Your design system is a CSS file, not a JavaScript object. That means zero hydration cost, instant theme switching, and compatibility with any SSR framework.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;12 tree-shakeable packages - install only what you use&lt;/li&gt;
&lt;li&gt;Radix UI accessibility internals (zero API leakage)&lt;/li&gt;
&lt;li&gt;5 theme presets with oklch perceptual colors&lt;/li&gt;
&lt;li&gt;98 &lt;code&gt;data-slot&lt;/code&gt; CSS targets for granular customization&lt;/li&gt;
&lt;li&gt;Full TypeScript generics on every component&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;→ &lt;a href="https://ninna-ui.dev" rel="noopener noreferrer"&gt;ninna-ui.dev&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  DaisyUI v5 - Semantic CSS Classes
&lt;/h3&gt;

&lt;p&gt;DaisyUI remains the go-to Tailwind plugin for developers who want semantic class names. v5 brought Tailwind v4 compatibility and oklch-based themes. If you're building static sites or prefer CSS-only components, DaisyUI is hard to beat.&lt;/p&gt;

&lt;p&gt;→ &lt;a href="https://daisyui.com" rel="noopener noreferrer"&gt;daisyui.com&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  shadcn/ui - Copy-Paste Components
&lt;/h3&gt;

&lt;p&gt;The copy-paste model that launched a thousand forks. shadcn/ui gives you full code ownership of Radix + Tailwind components. Great if you want to customize everything, but be prepared to manage updates yourself.&lt;/p&gt;

&lt;p&gt;→ &lt;a href="https://ui.shadcn.com" rel="noopener noreferrer"&gt;ui.shadcn.com&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Animation Libraries
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Tailwind CSS Animate
&lt;/h3&gt;

&lt;p&gt;The official-feeling animation plugin for Tailwind CSS. Provides utility classes for common CSS animations - &lt;code&gt;animate-in&lt;/code&gt;, &lt;code&gt;fade-in&lt;/code&gt;, &lt;code&gt;slide-in-from-top&lt;/code&gt;, &lt;code&gt;zoom-in&lt;/code&gt;, etc. Used extensively by shadcn/ui and other libraries.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;div&lt;/span&gt; &lt;span class="na"&gt;class=&lt;/span&gt;&lt;span class="s"&gt;"animate-in fade-in slide-in-from-bottom-4 duration-500"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
  Content appears with a smooth entrance
&lt;span class="nt"&gt;&amp;lt;/div&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In Tailwind v4, these integrate cleanly with the new &lt;code&gt;@source inline()&lt;/code&gt; safelist pattern if you're consuming them from npm.&lt;/p&gt;

&lt;h3&gt;
  
  
  Framer Motion
&lt;/h3&gt;

&lt;p&gt;Not Tailwind-specific, but Framer Motion remains the gold standard for React animations in 2026. Use it alongside Tailwind for complex gesture-driven and layout animations that CSS alone can't handle.&lt;/p&gt;

&lt;h3&gt;
  
  
  Motion One
&lt;/h3&gt;

&lt;p&gt;A lightweight alternative to Framer Motion (~3.5KB) built on the Web Animations API. Perfect when you want smooth animations without the bundle weight. Works great with Tailwind's utility classes for initial styling.&lt;/p&gt;

&lt;h2&gt;
  
  
  Typography &amp;amp; Content
&lt;/h2&gt;

&lt;h3&gt;
  
  
  &lt;a class="mentioned-user" href="https://dev.to/tailwindcss"&gt;@tailwindcss&lt;/a&gt;/typography
&lt;/h3&gt;

&lt;p&gt;The official typography plugin for beautiful prose content. Essential for blogs, documentation, and content-heavy pages. v4 brought simplified configuration:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="k"&gt;@plugin&lt;/span&gt; &lt;span class="s1"&gt;"@tailwindcss/typography"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Use the &lt;code&gt;prose&lt;/code&gt; class to get beautiful defaults for Markdown-rendered content, with full dark mode support.&lt;/p&gt;

&lt;h3&gt;
  
  
  Tailwind CSS Container Queries
&lt;/h3&gt;

&lt;p&gt;Container queries landed in all major browsers in 2024, and Tailwind v4 supports them natively with &lt;code&gt;@container&lt;/code&gt; variants. This eliminates the need for third-party plugins - just use &lt;code&gt;@container&lt;/code&gt; in your CSS or &lt;code&gt;@min-width&lt;/code&gt; / &lt;code&gt;@max-width&lt;/code&gt; in your Tailwind classes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Icon Libraries
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Lucide React
&lt;/h3&gt;

&lt;p&gt;The community-maintained fork of Feather Icons, Lucide provides 1500+ beautiful SVG icons as React components. Tree-shakeable, consistent 24×24 grid, and perfect with Tailwind's &lt;code&gt;size-*&lt;/code&gt; utilities:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Search&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;ArrowRight&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;Check&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;lucide-react&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Search&lt;/span&gt; &lt;span class="na"&gt;className&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"size-5 text-base-content/60"&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Heroicons
&lt;/h3&gt;

&lt;p&gt;Made by the Tailwind CSS team, Heroicons provides 300+ icons in outline, solid, and mini styles. Slightly smaller set than Lucide but with an extremely consistent visual language.&lt;/p&gt;

&lt;h3&gt;
  
  
  Phosphor Icons
&lt;/h3&gt;

&lt;p&gt;If you need variety, Phosphor offers 9,000+ icons across 6 weight variations (thin, light, regular, bold, fill, duotone). The React package is tree-shakeable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Developer Tools
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Tailwind CSS IntelliSense (VS Code)
&lt;/h3&gt;

&lt;p&gt;The official VS Code extension is essential. In 2026, it supports Tailwind v4's CSS-first configuration, providing autocomplete and hover previews for &lt;code&gt;@theme&lt;/code&gt; values, custom utilities, and &lt;code&gt;@variant&lt;/code&gt; definitions.&lt;/p&gt;

&lt;h3&gt;
  
  
  Prettier Plugin for Tailwind CSS
&lt;/h3&gt;

&lt;p&gt;Automatically sorts your Tailwind utility classes in a consistent, readable order. With v4, the plugin understands the new class naming patterns and works seamlessly.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pnpm add &lt;span class="nt"&gt;-D&lt;/span&gt; prettier-plugin-tailwindcss
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Tailwind Merge
&lt;/h3&gt;

&lt;p&gt;When building component libraries, &lt;code&gt;tailwind-merge&lt;/code&gt; is essential for resolving class conflicts. It ensures that when a consumer passes &lt;code&gt;className="p-4"&lt;/code&gt; to a component that already has &lt;code&gt;className="p-6"&lt;/code&gt;, the consumer's class wins:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;twMerge&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;tailwind-merge&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;Button&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="nx"&gt;className&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;...&lt;/span&gt;&lt;span class="nx"&gt;props&lt;/span&gt; &lt;span class="p"&gt;})&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;button&lt;/span&gt; &lt;span class="na"&gt;className&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nf"&gt;twMerge&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;px-4 py-2 bg-blue-500&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;className&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt; &lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="p"&gt;...&lt;/span&gt;&lt;span class="nx"&gt;props&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Ninna UI uses this internally via a &lt;code&gt;cn()&lt;/code&gt; utility (clsx + tailwind-merge).&lt;/p&gt;

&lt;h2&gt;
  
  
  Form Libraries
&lt;/h2&gt;

&lt;h3&gt;
  
  
  React Hook Form + Tailwind
&lt;/h3&gt;

&lt;p&gt;React Hook Form v8 remains the performance king for React forms. Pair it with Tailwind CSS components for a fast, accessible form experience:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;useForm&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;react-hook-form&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Input&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;Field&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@ninna-ui/forms&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Button&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@ninna-ui/primitives&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;LoginForm&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;register&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;handleSubmit&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;useForm&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
  &lt;span class="k"&gt;return &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;form&lt;/span&gt; &lt;span class="na"&gt;onSubmit&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nf"&gt;handleSubmit&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;onSubmit&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Field&lt;/span&gt; &lt;span class="na"&gt;label&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"Email"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
        &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Input&lt;/span&gt; &lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="p"&gt;...&lt;/span&gt;&lt;span class="nf"&gt;register&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;email&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt; &lt;span class="na"&gt;placeholder&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"you@example.com"&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Field&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Button&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"submit"&lt;/span&gt; &lt;span class="na"&gt;color&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"primary"&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;Sign In&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nc"&gt;Button&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;form&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Zod + Form Validation
&lt;/h3&gt;

&lt;p&gt;Zod continues to dominate TypeScript-first schema validation. Combined with React Hook Form's &lt;code&gt;zodResolver&lt;/code&gt;, you get end-to-end type-safe forms with zero runtime overhead from the validation layer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Build Tools
&lt;/h2&gt;

&lt;h3&gt;
  
  
  &lt;a class="mentioned-user" href="https://dev.to/tailwindcss"&gt;@tailwindcss&lt;/a&gt;/vite
&lt;/h3&gt;

&lt;p&gt;The official Vite plugin for Tailwind v4. Zero-config - just add it to your Vite config and import Tailwind in CSS:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nx"&gt;tailwindcss&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@tailwindcss/vite&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="nf"&gt;defineConfig&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="na"&gt;plugins&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nf"&gt;tailwindcss&lt;/span&gt;&lt;span class="p"&gt;()],&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  &lt;a class="mentioned-user" href="https://dev.to/tailwindcss"&gt;@tailwindcss&lt;/a&gt;/postcss
&lt;/h3&gt;

&lt;p&gt;For Next.js and other PostCSS-based setups. Same zero-config approach as the Vite plugin.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 2026 Tailwind Stack
&lt;/h2&gt;

&lt;p&gt;Here's what a modern Tailwind CSS stack looks like in 2026:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Layer&lt;/th&gt;
&lt;th&gt;Tool&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Framework&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;React 19 + Next.js 15 / Vite 7 / React Router v7&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Styling&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Tailwind CSS v4 (&lt;code&gt;@tailwindcss/vite&lt;/code&gt; or &lt;code&gt;@tailwindcss/postcss&lt;/code&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Components&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Ninna UI (69 accessible components, CSS-only theming)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Icons&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Lucide React (1500+ tree-shakeable icons)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Typography&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;
&lt;a class="mentioned-user" href="https://dev.to/tailwindcss"&gt;@tailwindcss&lt;/a&gt;/typography&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Animation&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;tailwindcss-animate + Framer Motion (when needed)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Forms&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;React Hook Form + Zod&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;DX&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Tailwind IntelliSense + Prettier plugin + tailwind-merge&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;This stack gives you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Zero runtime theming&lt;/strong&gt; (CSS custom properties)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;WCAG AA accessibility&lt;/strong&gt; (Radix internals)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Full type safety&lt;/strong&gt; (TypeScript generics throughout)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sub-second builds&lt;/strong&gt; (Lightning CSS engine)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tree-shakeable everything&lt;/strong&gt; (ESM packages)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://ninna-ui.dev/getting-started/installation" rel="noopener noreferrer"&gt;Try the full stack with Ninna UI&lt;/a&gt;&lt;/p&gt;

</description>
      <category>tailwindcss</category>
      <category>webdev</category>
      <category>frontend</category>
      <category>react</category>
    </item>
    <item>
      <title>Top 5 Free Tailwind Component Libraries in 2026</title>
      <dc:creator>Cihan Koç</dc:creator>
      <pubDate>Wed, 25 Mar 2026 20:42:57 +0000</pubDate>
      <link>https://dev.to/chnkc41/top-5-free-tailwind-component-libraries-in-2026-49f9</link>
      <guid>https://dev.to/chnkc41/top-5-free-tailwind-component-libraries-in-2026-49f9</guid>
      <description>&lt;p&gt;Building a production app shouldn't require a four-figure UI kit license. The Tailwind CSS ecosystem in 2026 has matured to the point where free, open-source component libraries rival-and in many cases surpass-their commercial counterparts.&lt;/p&gt;

&lt;p&gt;Here are the 5 best free Tailwind CSS component libraries you can use today, ranked by how well they solve the real problems developers face: &lt;strong&gt;accessibility&lt;/strong&gt;, &lt;strong&gt;theming&lt;/strong&gt;, &lt;strong&gt;type safety&lt;/strong&gt;, and &lt;strong&gt;Tailwind v4 compatibility&lt;/strong&gt;. Of course there are many other good components as well but we will check about Ninna ui, Daisyui, Shadcn ui, Flowbite ui and Preline ui.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Ninna UI - Zero-Runtime React Components
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/ninna-ui/ninna-ui" rel="noopener noreferrer"&gt;github.com/ninna-ui/ninna-ui&lt;/a&gt; · &lt;strong&gt;License:&lt;/strong&gt; MIT · &lt;strong&gt;Stars:&lt;/strong&gt; Growing fast&lt;/p&gt;

&lt;p&gt;Ninna UI is a full React component library purpose-built for Tailwind CSS v4 and React 19. Unlike CSS-only libraries, every component is a real React element with &lt;code&gt;forwardRef&lt;/code&gt;, &lt;code&gt;displayName&lt;/code&gt;, TypeScript generics, and Radix-powered accessibility.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why it stands out
&lt;/h3&gt;

&lt;p&gt;The killer feature is &lt;strong&gt;zero-runtime theming&lt;/strong&gt;. Most React UI libraries require a &lt;code&gt;ThemeProvider&lt;/code&gt; wrapper that adds JavaScript overhead and hydration cost. Ninna UI eliminates this entirely - your design system is a single CSS import:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight css"&gt;&lt;code&gt;&lt;span class="k"&gt;@import&lt;/span&gt; &lt;span class="s1"&gt;"tailwindcss"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;@import&lt;/span&gt; &lt;span class="s1"&gt;"@ninna-ui/core/theme/presets/default.css"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That's the complete setup. No &lt;code&gt;tailwind.config.ts&lt;/code&gt;. No &lt;code&gt;ExtraProvider&lt;/code&gt;. No &lt;code&gt;createTheme()&lt;/code&gt;. Just CSS.&lt;/p&gt;

&lt;h3&gt;
  
  
  What you get (for free)
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;69 components&lt;/strong&gt; across 12 tree-shakeable packages&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;5 theme presets&lt;/strong&gt; (Default, Ocean, Sunset, Forest, Minimal) - all oklch-based&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;WCAG 2.1 AA&lt;/strong&gt; accessibility on every component&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;98 data-slot CSS targets&lt;/strong&gt; for customizing any internal element&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;700+ tests&lt;/strong&gt; covering every component&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CLI scaffolding&lt;/strong&gt; - &lt;code&gt;npx @ninna-ui/cli init my-app&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Button&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;Badge&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@ninna-ui/primitives&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Modal&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@ninna-ui/overlays&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;DataTable&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@ninna-ui/data-display&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Best for
&lt;/h3&gt;

&lt;p&gt;React teams who want npm-installable, accessible components with native Tailwind CSS v4 theming and zero configuration overhead.&lt;/p&gt;

&lt;p&gt;→ &lt;a href="https://ninna-ui.dev/getting-started/installation" rel="noopener noreferrer"&gt;Get started&lt;/a&gt; · &lt;a href="https://ninna-ui.dev/examples" rel="noopener noreferrer"&gt;Live examples&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  2. DaisyUI - The Beloved CSS Plugin
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/saadeghi/daisyui" rel="noopener noreferrer"&gt;github.com/saadeghi/daisyui&lt;/a&gt; · &lt;strong&gt;License:&lt;/strong&gt; MIT · &lt;strong&gt;Stars:&lt;/strong&gt; 35k+&lt;/p&gt;

&lt;p&gt;DaisyUI v5 is the most popular Tailwind CSS component plugin. It adds semantic class names to Tailwind - &lt;code&gt;btn&lt;/code&gt;, &lt;code&gt;card&lt;/code&gt;, &lt;code&gt;modal&lt;/code&gt;, &lt;code&gt;badge&lt;/code&gt; - so you write less utility markup.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why it stands out
&lt;/h3&gt;

&lt;p&gt;DaisyUI's approach is beautifully simple: it's a Tailwind plugin that adds component classes. Zero JavaScript. Framework-agnostic. Works with any HTML. The 35 built-in themes (now with oklch colors in v5) let you switch design flavors instantly.&lt;/p&gt;

&lt;h3&gt;
  
  
  Limitations to consider
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;No accessibility&lt;/strong&gt; - CSS classes can't add ARIA attributes, manage focus, or handle keyboard navigation&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No TypeScript safety&lt;/strong&gt; - component "APIs" are class name strings&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Interactive components require manual JS&lt;/strong&gt; - dropdowns, modals, selects need your own implementation&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not React-native&lt;/strong&gt; - you're working with class names, not component props&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Best for
&lt;/h3&gt;

&lt;p&gt;Rapid prototyping, static sites, and projects where you handle interactivity and accessibility yourself.&lt;/p&gt;




&lt;h2&gt;
  
  
  3. shadcn/ui - Copy-Paste Components
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/shadcn-ui/ui" rel="noopener noreferrer"&gt;github.com/shadcn-ui/ui&lt;/a&gt; · &lt;strong&gt;License:&lt;/strong&gt; MIT · &lt;strong&gt;Stars:&lt;/strong&gt; 80k+&lt;/p&gt;

&lt;p&gt;shadcn/ui popularized a radical idea: instead of installing components from npm, you copy their source code directly into your project. A CLI handles the copying, and you get full ownership of every line.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why it stands out
&lt;/h3&gt;

&lt;p&gt;The code-ownership model means you can customize anything without fighting library abstractions. Components are built on Radix UI primitives with Tailwind CSS styling, giving you solid accessibility foundations.&lt;/p&gt;

&lt;h3&gt;
  
  
  Limitations to consider
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Manual updates&lt;/strong&gt; - no &lt;code&gt;npm update&lt;/code&gt;. When bugs are fixed upstream, you re-copy or manually patch&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dependency sprawl&lt;/strong&gt; - each component may pull in specific Radix packages as peer deps&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No versioning&lt;/strong&gt; - no changelogs, no semantic versioning, no migration guides&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Per-project forks&lt;/strong&gt; - every project gets a unique copy, making consistency across projects challenging&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Best for
&lt;/h3&gt;

&lt;p&gt;Solo developers or small teams who want complete control and are comfortable maintaining their own component code.&lt;/p&gt;




&lt;h2&gt;
  
  
  4. Flowbite - Cross-Framework UI Kit
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/themesberg/flowbite" rel="noopener noreferrer"&gt;github.com/themesberg/flowbite&lt;/a&gt; · &lt;strong&gt;License:&lt;/strong&gt; MIT (core) · &lt;strong&gt;Stars:&lt;/strong&gt; 8k+&lt;/p&gt;

&lt;p&gt;Flowbite provides Tailwind CSS components in vanilla HTML/JS with official React, Vue, and Svelte wrappers. The free tier is generous, though some advanced components and templates are behind a paid plan.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why it stands out
&lt;/h3&gt;

&lt;p&gt;If you work across frameworks - React for the app, Astro for the marketing site, Svelte for the dashboard - Flowbite gives you a consistent visual language everywhere. The vanilla core means components work with anything.&lt;/p&gt;

&lt;h3&gt;
  
  
  Limitations to consider
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;React wrappers are less polished&lt;/strong&gt; than the vanilla HTML versions&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Accessibility coverage varies&lt;/strong&gt; by component&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Some pro components are paywalled&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tailwind v4 support is still maturing&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Best for
&lt;/h3&gt;

&lt;p&gt;Multi-framework teams and projects that need consistent Tailwind components across React, Vue, and Svelte.&lt;/p&gt;




&lt;h2&gt;
  
  
  5. Preline UI - Large Component Library
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/htmlstreamofficial/preline" rel="noopener noreferrer"&gt;github.com/htmlstreamofficial/preline&lt;/a&gt; · &lt;strong&gt;License:&lt;/strong&gt; MIT · &lt;strong&gt;Stars:&lt;/strong&gt; 5k+&lt;/p&gt;

&lt;p&gt;Preline offers 70+ Tailwind CSS components with a vanilla JS plugin approach. It includes a large collection of marketing blocks, application UI, and landing page components.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why it stands out
&lt;/h3&gt;

&lt;p&gt;Preline has one of the largest free component collections in the Tailwind ecosystem. The marketing-focused blocks (hero sections, pricing tables, feature grids, testimonials) are particularly useful for landing pages.&lt;/p&gt;

&lt;h3&gt;
  
  
  Limitations to consider
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Vanilla JS plugin&lt;/strong&gt; - not React-native, requires manual integration&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Accessibility is partial&lt;/strong&gt; - not all interactive components have proper ARIA&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;TypeScript integration limited&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Less active maintenance&lt;/strong&gt; compared to top-tier libraries&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Best for
&lt;/h3&gt;

&lt;p&gt;Landing pages, marketing sites, and projects that need a large variety of pre-built sections.&lt;/p&gt;




&lt;h2&gt;
  
  
  Quick Comparison
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Ninna UI&lt;/th&gt;
&lt;th&gt;DaisyUI&lt;/th&gt;
&lt;th&gt;shadcn/ui&lt;/th&gt;
&lt;th&gt;Flowbite&lt;/th&gt;
&lt;th&gt;Preline&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Price&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Free (MIT)&lt;/td&gt;
&lt;td&gt;Free (MIT)&lt;/td&gt;
&lt;td&gt;Free (MIT)&lt;/td&gt;
&lt;td&gt;Free core&lt;/td&gt;
&lt;td&gt;Free (MIT)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Components&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;69&lt;/td&gt;
&lt;td&gt;65+&lt;/td&gt;
&lt;td&gt;40+&lt;/td&gt;
&lt;td&gt;44+&lt;/td&gt;
&lt;td&gt;70+&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;React-native&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;✅&lt;/td&gt;
&lt;td&gt;❌&lt;/td&gt;
&lt;td&gt;✅&lt;/td&gt;
&lt;td&gt;Wrapper&lt;/td&gt;
&lt;td&gt;❌&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Accessibility&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;WCAG AA&lt;/td&gt;
&lt;td&gt;None&lt;/td&gt;
&lt;td&gt;Radix-based&lt;/td&gt;
&lt;td&gt;Partial&lt;/td&gt;
&lt;td&gt;Partial&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Tailwind v4&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Native&lt;/td&gt;
&lt;td&gt;v5 plugin&lt;/td&gt;
&lt;td&gt;v3 + v4&lt;/td&gt;
&lt;td&gt;Early&lt;/td&gt;
&lt;td&gt;v3 + v4&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;TypeScript&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Full&lt;/td&gt;
&lt;td&gt;N/A&lt;/td&gt;
&lt;td&gt;Good&lt;/td&gt;
&lt;td&gt;Partial&lt;/td&gt;
&lt;td&gt;Limited&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Theming&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;5 CSS presets + CSS vars&lt;/td&gt;
&lt;td&gt;35 themes&lt;/td&gt;
&lt;td&gt;CSS vars&lt;/td&gt;
&lt;td&gt;CSS vars&lt;/td&gt;
&lt;td&gt;CSS vars&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Runtime cost&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Zero&lt;/td&gt;
&lt;td&gt;Zero&lt;/td&gt;
&lt;td&gt;Radix runtime&lt;/td&gt;
&lt;td&gt;Small JS&lt;/td&gt;
&lt;td&gt;Small JS&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Updates&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;npm update&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;npm update&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Manual copy&lt;/td&gt;
&lt;td&gt;&lt;code&gt;npm update&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;npm update&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;———&lt;br&gt;
Every library on this list is free and MIT-licensed. The choice comes down to your stack and priorities:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;React + best DX + accessibility&lt;/strong&gt; → Ninna UI&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Any framework + CSS-only simplicity&lt;/strong&gt; → DaisyUI&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Full code ownership&lt;/strong&gt; → shadcn/ui&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Multi-framework consistency&lt;/strong&gt; → Flowbite&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Maximum component variety&lt;/strong&gt; → Preline&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The trend in 2026 is unmistakable: CSS-first theming is winning over JavaScript runtime approaches. Libraries that embrace Tailwind CSS v4's native capabilities - &lt;code&gt;@import&lt;/code&gt; configuration, oklch colors, CSS-only dark mode - deliver better performance and simpler developer experience.&lt;/p&gt;

</description>
      <category>tailwindcss</category>
      <category>react</category>
      <category>opensource</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
