nitro_kit 2.0.0.beta.2 → 2.0.0.beta.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d426e47dadcb1efcc115e21074c210e35c4120fca8c4093abf1cc5c431689ce4
-  data.tar.gz: 04e353250240db16067074982096a1753afd7ba45f0da04675cff2621e48ac50
+  metadata.gz: 84caf95e1c63e0461bef9e9a0183b67d02bf3c00fee964f0d0ee321a23b5457f
+  data.tar.gz: 9ebac7e5aa8f5cc74f4930838b0760a364eaebc7f1d9a01d99d8a15ce152b135
 SHA512:
-  metadata.gz: b2874c385257fbaeae559112addd4702d06b12b510eefcde84c8408f422ce54e7326329f27d2843b420245abbde08acf95aa68f4fd85c69041ca6b477350910a
-  data.tar.gz: 153c7c83078bc7521af05540b4750ac3e82b5e5f99da6255c3372c37fa6ef3d1a084aad094e72f45d7da89a06dc294eb249f569dc67d9d8bfa594213a99945f4
+  metadata.gz: 56d6151cb701d8254ee9671d900f8053ddcd023435b03157f590dbad2f5f283e489f4db54e34de122996006af532c725cd86cc0491d48810b17fa343e1654da4
+  data.tar.gz: 482fa5ddf8c57c09c3f7d6f3e4e607fcd125dcecf8ff23500474cb8926469e73c139a4126610bf4df7e59d37ada2ea47d38e2bcc462649a95248cf7009424ac1

data/CHANGELOG.md

@@ -1,5 +1,46 @@
 # Changelog
 
+## 2.0.0.beta.3
+
+### Added
+
+- Ship `app/assets/tailwind/nitro_kit/engine.css` for `tailwindcss-rails`
+  engine support, so a Tailwind CSS v4 application can `@import
+"../builds/tailwind/nitro_kit"` and load Nitro Kit through its single
+  compiled `tailwind` stylesheet. The engine keeps that entry out of the asset
+  pipeline, and `nitro_kit:doctor` and the installer expect only `tailwind`
+  when the import is present.
+
+### Changed
+
+- Fold the Tailwind CSS v4 adapter into `nitro_kit.css`. The distribution
+  stylesheet now opens with the global cascade-layer order and carries the
+  Tailwind theme aliases from `src/stylesheets/nitro_kit/tailwind.css`, so a
+  Tailwind application links `nitro_kit` then `tailwind` and nothing else.
+
+### Fixed
+
+- Replace the invalid `::file-selector-button:disabled` reset selector with
+  `:disabled::file-selector-button`, which Lightning CSS otherwise warns about
+  when the stylesheet goes through a Tailwind build.
+
+### Removed
+
+- The separate `nitro_kit-tailwind-v4.css` asset. Remove it from the layout's
+  `stylesheet_link_tag`; `nitro_kit:doctor` flags a leftover link.
+
+### Upgrade notes
+
+- Pin `2.0.0.beta.3` explicitly. Beta releases may still change APIs; review
+  release notes before updating.
+- Delete `"nitro_kit-tailwind-v4"` from every `stylesheet_link_tag`. The
+  `nitro_kit` stylesheet now provides the cascade-layer order and Tailwind
+  theme aliases itself, and must load before the compiled `tailwind`
+  stylesheet. Run `nitro_kit:doctor` to confirm the layout.
+- A `tailwindcss-rails` application can optionally collapse to one stylesheet:
+  add `@import "../builds/tailwind/nitro_kit";` above `@import "tailwindcss";`
+  in `app/assets/tailwind/application.css` and link only `tailwind`.
+
 ## 2.0.0.beta.2
 
 ### Added
@@ -8,7 +49,7 @@
   stop hand-rolling headers and footers. `actions` inside a `header` trail the
   title and description; inside a `footer` they push to the end.
 - Add Card `size: :sm | :md | :lg` density and `variant: :default | :muted |
-  :outline` surfaces, emitted as owned `data-size` and `data-variant`
+:outline` surfaces, emitted as owned `data-size` and `data-variant`
   attributes. Sizes coordinate padding, part gaps, corners, and title size.
 - Add explicit `nitro_kit:eject COMPONENT` source-level customization, with
   isolated Ruby/CSS/Stimulus dependencies, version provenance, and safe whole-snapshot

data/README.md

@@ -6,7 +6,7 @@
 
 **Audience:** Rails developers evaluating or installing Nitro Kit.
 
-Nitro Kit is a gem-owned Phlex UI system for Rails. The `2.0.0.beta.2` prerelease
+Nitro Kit is a gem-owned Phlex UI system for Rails. The `2.0.0.beta.3` prerelease
 is under active testing and is not stable.
 
 [![RubyGems](https://img.shields.io/gem/v/nitro_kit.svg)](https://rubygems.org/gems/nitro_kit)
@@ -16,7 +16,7 @@ is under active testing and is not stable.
 Pin the prerelease:
 
 ```ruby
-gem "nitro_kit", "2.0.0.beta.2"
+gem "nitro_kit", "2.0.0.beta.3"
 ```
 
 ```sh

data/STYLE_GUIDE.md

@@ -330,7 +330,7 @@ Before JavaScript connects, `:root` follows `prefers-color-scheme`. Explicit `[d
 
 Customization tools may read, preview, and export documented public tokens. Model customizer state as an immutable, explicitly versioned value object with closed named choices and readable URL parameters; never serialize an opaque arbitrary-token blob. Exports use stable selector and declaration ordering, cover light, dark, and system fallback, and contain only documented public variables. Structural preview choices may emit copyable component-composition examples, but never component implementations. Customization tools must not expose private `--_nk-*` values, edit the generated distribution asset, generate component copies, or turn arbitrary CSS into a Nitro contract.
 
-The optional `nitro_kit-tailwind-v4.css` adapter is a separate asset. It may map Nitro values into Tailwind v4 theme variables, but Tailwind compilation, source detection, and utilities remain application concerns. Do not add Tailwind as a Nitro runtime dependency.
+`src/stylesheets/nitro_kit/tailwind.css` declares the global cascade-layer order and maps Nitro values into Tailwind v4 theme variables so a compiled Tailwind stylesheet composes with the distribution asset. Tailwind compilation, source detection, and utilities remain application concerns. Do not add Tailwind as a Nitro runtime dependency.
 
 ## Baseline
 

data/app/assets/stylesheets/nitro_kit.css

@@ -4,6 +4,14 @@
  */
 
 /* Source: src/stylesheets/nitro_kit/layers.css */
+/*
+ * Global cascade-layer order. Declared first so that, when an application also
+ * loads a compiled Tailwind CSS v4 stylesheet, Nitro Kit sits between
+ * Tailwind's base and components layers and Tailwind utilities still win.
+ * Without Tailwind the extra layers are simply unused.
+ */
+@layer properties, theme, base, nitro-kit, components, utilities;
+
 @layer nitro-kit.tokens,
   nitro-kit.reset,
   nitro-kit.base,
@@ -635,6 +643,45 @@
   }
 }
 
+/* Source: src/stylesheets/nitro_kit/tailwind.css */
+/*
+ * Tailwind CSS v4 theme aliases. Maps Nitro tokens onto the theme variables
+ * Tailwind utilities read, so bg-background, rounded-md, shadow-sm and friends
+ * share one palette with the components. Tailwind itself stays an application
+ * concern: Nitro Kit never compiles, configures, or depends on it.
+ */
+@layer nitro-kit.tokens {
+  :where(:root, [data-theme]) {
+    --font-sans: var(--nk-font-sans);
+    --font-mono: var(--nk-font-mono);
+    --spacing: var(--nk-space);
+
+    --color-background: var(--nk-color-canvas);
+    --color-foreground: var(--nk-color-foreground);
+    --color-muted: var(--nk-color-muted);
+    --color-muted-content: var(--nk-color-muted-foreground);
+    --color-border: var(--nk-color-border);
+    --color-ring: var(--nk-color-focus);
+    --color-primary: var(--nk-color-primary);
+    --color-primary-foreground: var(--nk-color-primary-foreground);
+    --color-destructive: var(--nk-color-destructive);
+    --color-destructive-content: var(--nk-color-destructive-content);
+    --color-destructive-foreground: var(--nk-color-destructive-foreground);
+
+    --radius-sm: var(--nk-radius-sm);
+    --radius-md: var(--nk-radius-md);
+    --radius-lg: var(--nk-radius-lg);
+    --radius-xl: var(--nk-radius-xl);
+
+    --shadow-sm: var(--nk-shadow-sm);
+    --shadow-md: var(--nk-shadow-md);
+    --shadow-lg: var(--nk-shadow-lg);
+
+    --default-transition-duration: var(--nk-duration-normal);
+    --default-transition-timing-function: var(--nk-ease);
+  }
+}
+
 /* Source: src/stylesheets/nitro_kit/reset.css */
 /* Nitro Kit ships its own full-page preflight. It lives in the
    `nitro-kit.reset` cascade layer, so unlayered application CSS always wins,
@@ -754,7 +801,7 @@
   }
 
   :where(:disabled),
-  ::file-selector-button:disabled {
+  :disabled::file-selector-button {
     cursor: default;
   }
 

data/app/assets/tailwind/nitro_kit/engine.css

@@ -0,0 +1,15 @@
+/*
+ * Nitro Kit entry point for tailwindcss-rails engine support.
+ *
+ * tailwindcss-rails writes app/assets/builds/tailwind/nitro_kit.css in the host
+ * application on every build or watch. Importing that file from the host's
+ * app/assets/tailwind/application.css bundles Nitro Kit into the single
+ * compiled Tailwind stylesheet:
+ *
+ *   @import "../builds/tailwind/nitro_kit";
+ *   @import "tailwindcss";
+ *
+ * Nitro Kit leads so its cascade-layer order and Tailwind theme aliases apply
+ * to the whole file, matching the stylesheet order in docs/customization.md.
+ */
+@import "../../stylesheets/nitro_kit.css";

data/docs/browser_support.md

@@ -73,7 +73,13 @@ every possible descendant selector.
 ## Release verification
 
 Automated CI runs the full system suite in Chrome and priority browser smoke
-coverage in Firefox and macOS Safari. Before a release, maintainers also verify
+coverage in Firefox and macOS Safari. The Chrome lane runs headed under Xvfb
+with a single worker. Headless Linux Chrome reports no `hover` or `pointer`
+capability, so hover-gated behaviour such as the sidebar rail peek and tooltips
+never engages there, and parallel headed windows share one X pointer whose
+enter and leave events reset `:hover` while a test is mid-interaction. Linux
+and Windows also reserve a classic scrollbar gutter that macOS does not, so
+geometry assertions must not assume overlay scrollbars. Before a release, maintainers also verify
 the priority flows on current Android Chrome and iOS Safari. Capability-focused
 tests supplement these runs; they do not prove an untested historical browser
 version.

data/docs/component_contracts.md

@@ -4,7 +4,7 @@
 API. This table is also parsed by the gallery; keep every row to four cells and
 escape literal pipe characters.
 
-This is the shipped public catalog for `2.0.0.beta.2`. It records current Ruby
+This is the shipped public catalog for `2.0.0.beta.3`. It records current Ruby
 construction, rendered roots, closed vocabularies, compound cardinalities, and
 integration boundaries. For task guidance, start with the
 [agent guide](agent_guide.md) or [Rails integration](rails_integration.md).

data/docs/customization.md

@@ -11,10 +11,9 @@ Nitro Kit owns component Ruby, markup, behavior, and default CSS. Applications n
 Load browser styles in this order:
 
 1. Optional third-party base styles, such as Lexxy.
-2. The optional `nitro_kit-tailwind-v4` adapter.
-3. The generated `nitro_kit` distribution stylesheet.
-4. The application's compiled Tailwind CSS, when present.
-5. Application styles, including Nitro token overrides.
+2. The generated `nitro_kit` distribution stylesheet.
+3. The application's compiled Tailwind CSS, when present.
+4. Application styles, including Nitro token overrides.
 
 `NitroKit::AppearanceBootstrap` precedes every entry in this list. The install
 generator applies this order when it can identify conventional layout entries
@@ -34,14 +33,35 @@ A Rails application without Tailwind can use:
 A Tailwind CSS v4 application can use:
 
 ```erb
-<%= stylesheet_link_tag \
-  "nitro_kit-tailwind-v4", \
-  "nitro_kit", \
-  "tailwind", \
-  "application", \
-  "data-turbo-track": "reload" %>
+<%= stylesheet_link_tag "nitro_kit", "tailwind", "application", "data-turbo-track": "reload" %>
 ```
 
+`nitro_kit.css` opens with the global cascade-layer order
+`properties, theme, base, nitro-kit, components, utilities` and aliases Nitro
+tokens onto Tailwind's theme variables, so it must load before the compiled
+Tailwind stylesheet. The separate `nitro_kit-tailwind-v4` adapter from earlier
+2.0 betas no longer exists; `nitro_kit:doctor` reports a leftover link.
+
+A Tailwind CSS v4 application using `tailwindcss-rails` can instead ship one
+stylesheet. Nitro Kit provides the engine entry `tailwindcss-rails` looks for,
+`app/assets/tailwind/nitro_kit/engine.css`, and `tailwindcss:build` or
+`tailwindcss:watch` generates `app/assets/builds/tailwind/nitro_kit.css` in the
+application. Import it before Tailwind in `app/assets/tailwind/application.css`:
+
+```css
+@import "../builds/tailwind/nitro_kit";
+@import "tailwindcss";
+```
+
+Then the layout loads only the compiled Tailwind stylesheet:
+
+```erb
+<%= stylesheet_link_tag "tailwind", "application", "data-turbo-track": "reload" %>
+```
+
+`nitro_kit:doctor` recognizes the import and reports a separate `nitro_kit`
+link as a duplicate.
+
 Keep overrides unlayered in application CSS and load them after Nitro Kit. Nitro's selectors use `:where()` inside named cascade layers, so an ordinary application rule can override a token without selector escalation or `!important`.
 
 Do not edit `app/assets/stylesheets/nitro_kit.css` in the gem or a bundled copy of it. That file is generated from `src/stylesheets/nitro_kit/` and is replaced on upgrade. Variables named `--_nk-*` are private component mechanics and may change without notice. Only the `--nk-*` variables listed below are the customization contract.
@@ -472,9 +492,9 @@ This registers Nitro's `controllers/nk/*` modules together with application cont
 For the resulting behavior when those modules are not registered, use the
 canonical no-JavaScript matrix in [`browser_support.md`](browser_support.md).
 
-## Optional Tailwind CSS v4 adapter
+## Tailwind CSS v4 theme aliases
 
-Nitro Kit does not require Tailwind, Tailwind configuration, or Tailwind Preflight — it ships its own global preflight in the `nitro-kit.reset` cascade layer, which unlayered application CSS always overrides. The optional `nitro_kit-tailwind-v4.css` asset only establishes compatible cascade-layer order and maps Nitro tokens to common Tailwind v4 theme variables, including background, foreground, primary, destructive, radii, shadows, fonts, spacing, and transition defaults.
+Nitro Kit does not require Tailwind, Tailwind configuration, or Tailwind Preflight — it ships its own global preflight in the `nitro-kit.reset` cascade layer, which unlayered application CSS always overrides. For applications that do compile Tailwind, `nitro_kit.css` establishes a compatible cascade-layer order and maps Nitro tokens to common Tailwind v4 theme variables, including background, foreground, primary, destructive, radii, shadows, fonts, spacing, and transition defaults. The aliases live in `src/stylesheets/nitro_kit/tailwind.css` inside the `nitro-kit.tokens` layer; without Tailwind they are inert custom properties.
 
 Tailwind remains compiled and configured by the application. An application can add further aliases in its Tailwind CSS source with the v4 CSS-first API:
 
@@ -488,7 +508,7 @@ Tailwind remains compiled and configured by the application. An application can
 }
 ```
 
-Use `@theme inline` when a Tailwind theme variable references another custom property so generated utilities resolve the live Nitro value. The adapter does not make Tailwind a Nitro runtime dependency, configure source detection, generate utility classes, or permit Tailwind classes inside Nitro component APIs.
+Use `@theme inline` when a Tailwind theme variable references another custom property so generated utilities resolve the live Nitro value. The aliases do not make Tailwind a Nitro runtime dependency, configure source detection, generate utility classes, or permit Tailwind classes inside Nitro component APIs.
 
 ## Public token reference
 

data/docs/migration_1_to_2.md

@@ -12,7 +12,7 @@ Treat a 1.x migration as a product-flow review, not a helper rename. Nitro Kit
 Add the 2.0 prerelease to the application's Gemfile:
 
 ```ruby
-gem "nitro_kit", "2.0.0.beta.2"
+gem "nitro_kit", "2.0.0.beta.3"
 ```
 
 Bundler records the exact released version in `Gemfile.lock`; commit `Gemfile`

data/docs/rails_integration.md

@@ -12,7 +12,7 @@ There are no `nk_form_with` helpers or general ERB component bridge.
 Pin the current prerelease:
 
 ```ruby
-gem "nitro_kit", "2.0.0.beta.2"
+gem "nitro_kit", "2.0.0.beta.3"
 ```
 
 Use the released gem and commit `Gemfile` with `Gemfile.lock`. Before upgrading,
@@ -36,7 +36,9 @@ Load Nitro Kit before application styles:
 ```
 
 For third-party base CSS, Tailwind, appearance setup, and token overrides, use
-the canonical [stylesheet order](customization.md#stylesheet-order).
+the canonical [stylesheet order](customization.md#stylesheet-order). A
+`tailwindcss-rails` application can bundle Nitro Kit into its compiled Tailwind
+stylesheet through the engine entry described there.
 
 ## Stimulus
 

data/lib/nitro_kit/engine.rb

@@ -1,7 +1,12 @@
 module NitroKit
   class Engine < ::Rails::Engine
+    # Rails would otherwise derive "nitro_kit_engine". tailwindcss-rails looks up
+    # app/assets/tailwind/<engine_name>/engine.css, so the name is public.
+    engine_name "nitro_kit"
+
     IMPORTMAP_PATH = root.join("config/importmap.rb")
     JAVASCRIPT_PATHS = [ root.join("app/javascript") ].freeze
+    TAILWIND_PATH = root.join("app/assets/tailwind")
 
     initializer "nitro_kit.assets" do |app|
       next unless app.config.respond_to?(:assets)
@@ -11,6 +16,14 @@ module NitroKit
       end
     end
 
+    # The Tailwind engine entry is a build input for tailwindcss-rails, not a
+    # servable asset. Keep it out of Propshaft's load path.
+    initializer "nitro_kit.exclude_tailwind_path", before: "propshaft.append_assets_path" do |app|
+      next unless app.config.respond_to?(:assets) && app.config.assets.respond_to?(:excluded_paths)
+
+      app.config.assets.excluded_paths << TAILWIND_PATH unless app.config.assets.excluded_paths.include?(TAILWIND_PATH)
+    end
+
     initializer "nitro_kit.importmap", before: "importmap" do |app|
       next unless app.config.respond_to?(:importmap)
 

data/lib/nitro_kit/installation.rb

@@ -9,9 +9,13 @@ module NitroKit
     ROOT = Pathname.new(File.expand_path("../..", __dir__))
     SKILLS = %w[nitro-kit-hotwire nitro-kit-rails nitro-kit-ui].freeze
     SKILL_ROOTS = [ ".agents/skills", ".claude/skills" ].freeze
+    # nitro_kit-tailwind-v4 is the beta-era adapter that nitro_kit.css absorbed;
+    # it stays managed so doctor flags a leftover link instead of ignoring it.
     MANAGED_STYLESHEETS = %w[
       lexxy nitro_kit-tailwind-v4 nitro_kit tailwind application
     ].freeze
+    TAILWIND_ENTRY = "app/assets/tailwind/application.css"
+    TAILWIND_BUNDLE_IMPORT = %r{@import\s+["'](?:\.\./)+builds/tailwind/nitro_kit(?:\.css)?["']}
     AGENTS_START = "<!-- nitro-kit:start -->"
     AGENTS_END = "<!-- nitro-kit:end -->"
     AGENTS_BLOCK = <<~MARKDOWN.freeze
@@ -217,8 +221,12 @@ module NitroKit
           errors << "installer left the layout unchanged: #{edit_error}"
         end
 
-        if assets.include?("nitro_kit-tailwind-v4") && !expected.include?("tailwind")
-          errors << "remove nitro_kit-tailwind-v4 or load compiled Tailwind after nitro_kit"
+        if assets.include?("nitro_kit-tailwind-v4")
+          errors << "remove stylesheet \"nitro_kit-tailwind-v4\"; nitro_kit now includes the Tailwind v4 layer order and theme aliases"
+        end
+
+        if tailwind_bundles_nitro_kit? && assets.include?("nitro_kit")
+          errors << "remove stylesheet \"nitro_kit\"; #{TAILWIND_ENTRY} already bundles it"
         end
 
         bootstrap_position = analysis.bootstraps.first&.range&.begin
@@ -569,17 +577,20 @@ module NitroKit
         assets = managed_stylesheet_assets(analysis) - [ "nitro_kit-tailwind-v4" ]
         assets << "lexxy" if dependency?("lexxy")
         assets << "tailwind" if tailwind?(assets)
-        assets << "nitro_kit"
+        if tailwind_bundles_nitro_kit?
+          assets -= [ "nitro_kit" ]
+          assets << "tailwind"
+        else
+          assets << "nitro_kit"
+        end
         assets << "application" if assets.include?("application") || application_stylesheet_asset?
-        assets << "nitro_kit-tailwind-v4" if assets.include?("tailwind")
         ordered_stylesheets(assets.uniq)
       end
 
       def ordered_stylesheets(assets)
-        vendor = assets - %w[nitro_kit-tailwind-v4 nitro_kit tailwind application]
+        vendor = assets - %w[nitro_kit tailwind application]
         [
           *vendor,
-          *(%w[nitro_kit-tailwind-v4] & assets),
           *(%w[nitro_kit] & assets),
           *(%w[tailwind] & assets),
           *(%w[application] & assets)
@@ -597,6 +608,9 @@ module NitroKit
 
         existing = managed_stylesheet_assets(analysis)
         return "duplicate canonical stylesheet assets require manual review" if existing.uniq != existing
+        if existing.include?("nitro_kit-tailwind-v4")
+          return "drop \"nitro_kit-tailwind-v4\" from its stylesheet call without changing the call's options"
+        end
         unless existing == expected.select { existing.include?(_1) }
           return "existing canonical stylesheets are misordered; reorder their intact calls manually"
         end
@@ -657,7 +671,15 @@ module NitroKit
       end
 
       def tailwind?(assets)
-        assets.include?("tailwind") || dependency?("tailwindcss-rails") || application_root.join("app/assets/tailwind/application.css").file?
+        assets.include?("tailwind") || dependency?("tailwindcss-rails") || application_root.join(TAILWIND_ENTRY).file?
+      end
+
+      # True when the application's Tailwind source imports the engine entry
+      # that tailwindcss-rails generates from app/assets/tailwind/nitro_kit/engine.css,
+      # so the compiled "tailwind" stylesheet already contains Nitro Kit.
+      def tailwind_bundles_nitro_kit?
+        entry = application_root.join(TAILWIND_ENTRY)
+        entry.file? && entry.read.match?(TAILWIND_BUNDLE_IMPORT)
       end
 
       def application_stylesheet_asset?

data/lib/nitro_kit/version.rb

@@ -1,3 +1,3 @@
 module NitroKit
-  VERSION = "2.0.0.beta.2"
+  VERSION = "2.0.0.beta.3"
 end

data/lib/tasks/nitro_kit_tasks.rake

@@ -9,7 +9,7 @@ module NitroKit
     ROOT = Pathname.new(File.expand_path("../..", __dir__))
     SOURCE_ROOT = ROOT.join("src/stylesheets/nitro_kit")
     OUTPUT = ROOT.join("app/assets/stylesheets/nitro_kit.css")
-    FOUNDATION_SOURCES = %w[ layers.css tokens.css reset.css ].freeze
+    FOUNDATION_SOURCES = %w[ layers.css tokens.css tailwind.css reset.css ].freeze
     BANNER = <<~CSS.freeze
       /*
        * Nitro Kit 2.0

data/src/stylesheets/nitro_kit/layers.css

@@ -1,3 +1,11 @@
+/*
+ * Global cascade-layer order. Declared first so that, when an application also
+ * loads a compiled Tailwind CSS v4 stylesheet, Nitro Kit sits between
+ * Tailwind's base and components layers and Tailwind utilities still win.
+ * Without Tailwind the extra layers are simply unused.
+ */
+@layer properties, theme, base, nitro-kit, components, utilities;
+
 @layer nitro-kit.tokens,
   nitro-kit.reset,
   nitro-kit.base,

data/src/stylesheets/nitro_kit/reset.css

@@ -116,7 +116,7 @@
   }
 
   :where(:disabled),
-  ::file-selector-button:disabled {
+  :disabled::file-selector-button {
     cursor: default;
   }
 

data/{app/assets/stylesheets/nitro_kit-tailwind-v4.css → src/stylesheets/nitro_kit/tailwind.css}

@@ -1,10 +1,9 @@
 /*
- * Nitro Kit Tailwind CSS v4 adapter.
- * Load this before both Nitro Kit and compiled Tailwind stylesheets.
+ * Tailwind CSS v4 theme aliases. Maps Nitro tokens onto the theme variables
+ * Tailwind utilities read, so bg-background, rounded-md, shadow-sm and friends
+ * share one palette with the components. Tailwind itself stays an application
+ * concern: Nitro Kit never compiles, configures, or depends on it.
  */
-
-@layer properties, theme, base, nitro-kit, components, utilities;
-
 @layer nitro-kit.tokens {
   :where(:root, [data-theme]) {
     --font-sans: var(--nk-font-sans);

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: nitro_kit
 version: !ruby/object:Gem::Version
-  version: 2.0.0.beta.2
+  version: 2.0.0.beta.3
 platform: ruby
 authors:
 - Mikkel Malmberg
@@ -92,8 +92,8 @@ files:
 - LICENSE
 - README.md
 - STYLE_GUIDE.md
-- app/assets/stylesheets/nitro_kit-tailwind-v4.css
 - app/assets/stylesheets/nitro_kit.css
+- app/assets/tailwind/nitro_kit/engine.css
 - app/components/nitro_kit/accordion.rb
 - app/components/nitro_kit/alert.rb
 - app/components/nitro_kit/app_navigation.rb
@@ -270,6 +270,7 @@ files:
 - src/stylesheets/nitro_kit/components/typeset.css
 - src/stylesheets/nitro_kit/layers.css
 - src/stylesheets/nitro_kit/reset.css
+- src/stylesheets/nitro_kit/tailwind.css
 - src/stylesheets/nitro_kit/tokens.css
 homepage: https://nitrokit.dev
 licenses: