@thespielplatz/tsp-tools-theme 0.1.0 → 0.1.2

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.
Files changed (2) hide show
  1. package/README.md +18 -3
  2. package/package.json +10 -8
package/README.md CHANGED
@@ -169,9 +169,24 @@ The mode groups are written for both layouts: `.dark .tsp-theme` (scoped) **and*
169
169
  ## CSS ownership
170
170
 
171
171
  `assets/css/theme.css` owns the framework import (`@import "tailwindcss"; @import "@nuxt/ui";`)
172
- so a consumer does **not** add its own. A scoped consumer that already imports the framework in
173
- its own stylesheet should drop that import and let this layer provide it (then keep only its own
174
- app-specific tokens in a CSS file with no framework import).
172
+ and is added to the Nuxt `css` array automatically when you extend the layer. How a consumer
173
+ handles its own CSS depends on whether it has **its own `@theme`**:
174
+
175
+ - **No own design tokens** (global apps, or scoped apps whose non-themed area uses plain Nuxt UI):
176
+ you don't need any framework import — the layer provides it. If you had your own
177
+ `@import "tailwindcss"`, drop it.
178
+ - **Has its own `@theme`** (e.g. a scoped app with a separate public-area palette/fonts): **keep**
179
+ your own `@import "tailwindcss"; @import "@nuxt/ui";` in that stylesheet. A `@theme` block only
180
+ compiles inside a Tailwind entry, so it can't piggyback on this layer's stylesheet — yours is a
181
+ separate Tailwind graph. The duplicate import is intentional and harmless: both graphs share the
182
+ same runtime CSS variables, and `.tsp-theme` only re-points Nuxt UI's variables inside the themed
183
+ subtree.
184
+
185
+ > Proven by the piggybank adoption: the public Piggy palette stays in the app's own
186
+ > `main.css` (its own Tailwind entry); the admin tsp tokens come from this layer's `theme.css`.
187
+
188
+ The layer's stylesheet is also exposed for manual import if you ever need it:
189
+ `@import "@thespielplatz/tsp-tools-theme/assets/css/theme.css"`.
175
190
 
176
191
  ---
177
192
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@thespielplatz/tsp-tools-theme",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "description": "tsp.tools design-system theme as a Nuxt layer (Nuxt UI v4 + Tailwind v4): amber-on-anthracite tokens (light + dark), Nunito/Space Grotesk fonts, per-area colour mode, and the shared app shell. Use globally via `extends`, or scoped to a sub-area.",
5
5
  "author": "inf0matics",
6
6
  "license": "MIT",
@@ -26,7 +26,9 @@
26
26
  "access": "public"
27
27
  },
28
28
  "exports": {
29
- ".": "./nuxt.config.ts"
29
+ ".": "./nuxt.config.ts",
30
+ "./assets/css/theme.css": "./assets/css/theme.css",
31
+ "./package.json": "./package.json"
30
32
  },
31
33
  "main": "./nuxt.config.ts",
32
34
  "files": [
@@ -49,7 +51,7 @@
49
51
  "bump-patch": "npx changelogen@latest --release"
50
52
  },
51
53
  "dependencies": {
52
- "@nuxt/ui": "^4.3.0"
54
+ "@nuxt/ui": "^4.10.0"
53
55
  },
54
56
  "peerDependencies": {
55
57
  "@iconify-json/tabler": "^1.2.0",
@@ -61,11 +63,11 @@
61
63
  }
62
64
  },
63
65
  "devDependencies": {
64
- "@iconify-json/tabler": "^1.2.35",
65
- "@nuxt/eslint-config": "^1.12.1",
66
+ "@iconify-json/tabler": "^1.2.37",
67
+ "@nuxt/eslint-config": "^1.16.0",
66
68
  "changelogen": "^0.6.2",
67
- "eslint": "^9.39.2",
68
- "nuxt": "^4.2.2",
69
- "vue-tsc": "3.2.2"
69
+ "eslint": "^10.8.0",
70
+ "nuxt": "^4.5.1",
71
+ "vue-tsc": "3.3.8"
70
72
  }
71
73
  }