@sudajs/cli 0.18.3 → 0.18.5

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sudajs/cli",
3
- "version": "0.18.3",
3
+ "version": "0.18.5",
4
4
  "type": "module",
5
5
  "bin": {
6
6
  "suda": "./bin/suda.js"
@@ -25,7 +25,7 @@
25
25
  },
26
26
  "dependencies": {
27
27
  "@modelcontextprotocol/sdk": "^1.29.0",
28
- "@puckeditor/core": "^0.22.0",
28
+ "@puckeditor/core": "^0.22.4",
29
29
  "commander": "^12.1.0",
30
30
  "esbuild": "^0.25.12",
31
31
  "lucide-react": "^1.17.0",
@@ -34,7 +34,7 @@
34
34
  "react": "^19.2.7",
35
35
  "react-dom": "^19.2.7",
36
36
  "zod": "^3.24.1",
37
- "@sudajs/theme-engine": "6.3.0"
37
+ "@sudajs/theme-engine": "6.3.2"
38
38
  },
39
39
  "devDependencies": {
40
40
  "@tailwindcss/postcss": "^4.3.0",
@@ -922,10 +922,28 @@ radius, shadows, or spacing.
922
922
  and apply `createThemeDesignCssVariables(tokens)` to the theme root element.
923
923
  Components should consume CSS variables; they should not resolve design
924
924
  presets themselves.
925
- - In `src/styles.css`, map Suda variables to theme-local or Tailwind variables
926
- once, for example `--color-primary: var(--suda-color-primary, #...)` and
927
- `--radius-card: var(--suda-radius-card, 24px)`. Use those variables across
928
- sections, cards, CMS layouts, post lists, forms, and local blocks.
925
+ - Pure Tailwind themes should map Suda tokens only through `@theme inline`, then
926
+ consume utilities such as `bg-primary`, `text-primary-foreground`, and
927
+ `rounded-card`. The `inline` keyword is required so generated utilities read
928
+ `--suda-*` on the rendered theme root instead of resolving a `--color-*`
929
+ alias on `:root`.
930
+ - Hand-written CSS classes must consume `--suda-*` directly. Do not use
931
+ `var(--color-primary)`, `var(--color-background)`, `var(--radius-card)`, or
932
+ another Suda-backed alias declared by `@theme inline`; those compiler aliases
933
+ live on `:root` while Suda injects editable tokens on the descendant theme
934
+ root in production.
935
+ - When hand-written CSS needs a derived value, declare a theme-prefixed custom
936
+ property on the theme root and consume that property, for example:
937
+ ```css
938
+ .my-theme-root {
939
+ --my-theme-primary-hover: color-mix(in srgb, var(--suda-color-primary) 84%, black);
940
+ }
941
+ .my-theme-button:hover {
942
+ background: var(--my-theme-primary-hover);
943
+ }
944
+ ```
945
+ `suda theme check`, build, and publish reject hand-written consumption of
946
+ Suda-backed `@theme inline` aliases.
929
947
  - Keep typography and spacing scales centralized in `src/styles.css`. Define
930
948
  reusable classes or variables for containers, section padding, headings,
931
949
  eyebrow text, body copy, cards, buttons, inputs, and media frames. Reuse those
@@ -19,7 +19,7 @@
19
19
  "devDependencies": {
20
20
  "@eslint/js": "^9.39.4",
21
21
  "@tailwindcss/postcss": "^4.3.0",
22
- "@puckeditor/core": "^0.22.0",
22
+ "@puckeditor/core": "^0.22.4",
23
23
  "@sudajs/cli": "*",
24
24
  "@sudajs/theme-engine": "*",
25
25
  "@types/node": "^24.13.2",
@@ -42,7 +42,7 @@
42
42
  "vite": "^8.1.0"
43
43
  },
44
44
  "peerDependencies": {
45
- "@puckeditor/core": "^0.22.0",
45
+ "@puckeditor/core": "^0.22.4",
46
46
  "@sudajs/theme-engine": "*",
47
47
  "lucide-react": "^1.17.0",
48
48
  "react": "^19.2.7",