@foundrykit/tailwind 1.0.6 → 1.0.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # @foundrykit/tailwind
2
2
 
3
+ ## 1.0.7
4
+
5
+ ### Patch Changes
6
+
7
+ - [#129](https://github.com/umi-labs/foundry/pull/129) [`dad73bd`](https://github.com/umi-labs/foundry/commit/dad73bdf46b3de1b3b6db52ceb4465516ebdb7e1) Thanks [@sneddonisaac](https://github.com/sneddonisaac)! - Adds the `.theme-switching * { transition: none !important }` guard used by `ThemeToggle`. Documents the `@source "../node_modules/@foundrykit";` line pnpm sites must add to their `globals.css`: under pnpm this stylesheet resolves from inside `node_modules/.pnpm`, so it can't reach the site's installed FoundryKit packages on its own.
8
+
3
9
  ## 1.0.6
4
10
 
5
11
  ### Patch Changes
package/README.md CHANGED
@@ -23,6 +23,22 @@ This pulls in Tailwind v4, the animation utilities, and the FoundryKit token
23
23
  variables (`--background`, `--foreground`, `--primary`, chart colors, etc.),
24
24
  which are consumed by FoundryKit components.
25
25
 
26
+ ### Scanning FoundryKit packages (pnpm)
27
+
28
+ Tailwind does not scan `node_modules`, and under pnpm this stylesheet resolves
29
+ from `node_modules/.pnpm/...`, so it cannot point at your installed packages
30
+ itself. Add an `@source` line next to the import so the classes used inside
31
+ `@foundrykit/primitives`, `components`, `blocks` and friends are generated:
32
+
33
+ ```css
34
+ @import "@foundrykit/tailwind/globals.css";
35
+ /* Path is relative to this CSS file: adjust the ../ depth to reach node_modules. */
36
+ @source "../node_modules/@foundrykit";
37
+ ```
38
+
39
+ Without it, components render unstyled wherever they use a class your own code
40
+ does not.
41
+
26
42
  ## Exports
27
43
 
28
44
  - `@foundrykit/tailwind/globals.css` — the complete Tailwind v4 theme and tokens.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@foundrykit/tailwind",
3
- "version": "1.0.6",
3
+ "version": "1.0.7",
4
4
  "type": "module",
5
5
  "private": false,
6
6
  "publishConfig": {
package/src/globals.css CHANGED
@@ -7,7 +7,10 @@
7
7
  /* Scan every workspace package: primitives, blocks, components, etc. */
8
8
  @source "../../*/{src,dist}/**/*.{ts,tsx,js,jsx,mjs,cjs}";
9
9
 
10
- /* When consumed from npm: scan installed @foundrykit packages */
10
+ /* When consumed from npm with a flat node_modules (npm, yarn). Under pnpm this
11
+ file resolves inside node_modules/.pnpm, so no relative path from here reaches
12
+ the site's packages: pnpm sites must add
13
+ `@source "../node_modules/@foundrykit";` to their own globals.css (see README). */
11
14
  @source "../../../node_modules/@foundrykit/**/*.{ts,tsx,js,jsx,mjs,cjs}";
12
15
 
13
16
  @custom-variant dark (&:is(.dark *));
@@ -270,3 +273,10 @@
270
273
  cursor: pointer;
271
274
  }
272
275
  }
276
+
277
+ /* Set on <html> while the theme flips (see ThemeToggle) so colours swap in one
278
+ frame instead of every element transitioning at its own speed. */
279
+ .theme-switching * {
280
+ /* biome-ignore lint/complexity/noImportantStyles: must beat every component's own transition */
281
+ transition: none !important;
282
+ }
@@ -1,5 +0,0 @@
1
-
2
- > @foundrykit/tailwind@1.0.6 build /home/runner/work/foundry/foundry/packages/tailwind
3
- > echo 'No build required for CSS package'
4
-
5
- No build required for CSS package
@@ -1,5 +0,0 @@
1
-
2
- > @foundrykit/tailwind@1.0.6 type-check /home/runner/work/foundry/foundry/packages/tailwind
3
- > echo 'No TypeScript files to check'
4
-
5
- No TypeScript files to check