uniweb 0.12.38 → 0.12.40

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": "uniweb",
3
- "version": "0.12.38",
3
+ "version": "0.12.40",
4
4
  "description": "Create structured Vite + React sites with content/code separation",
5
5
  "type": "module",
6
6
  "bin": {
@@ -41,12 +41,12 @@
41
41
  "js-yaml": "^4.1.0",
42
42
  "prompts": "^2.4.2",
43
43
  "tar": "^7.0.0",
44
- "@uniweb/core": "0.7.14",
45
- "@uniweb/kit": "0.9.18",
46
- "@uniweb/runtime": "0.8.20"
44
+ "@uniweb/core": "0.7.16",
45
+ "@uniweb/kit": "0.9.20",
46
+ "@uniweb/runtime": "0.8.22"
47
47
  },
48
48
  "peerDependencies": {
49
- "@uniweb/build": "0.14.21",
49
+ "@uniweb/build": "0.14.23",
50
50
  "@uniweb/content-reader": "1.1.12",
51
51
  "@uniweb/semantic-parser": "1.1.17"
52
52
  },
@@ -1011,29 +1011,20 @@ Most customization is handled by component params. Both section components and l
1011
1011
 
1012
1012
  Foundation-level CSS variables are for values that must stay consistent **across** multiple components — shared radii, spacing scales, or additional font roles beyond the three the theming system already provides (body, heading, mono). Don't reach for foundation vars when a component or layout param would do.
1013
1013
 
1014
- If you need them, declare vars in two places:
1015
-
1016
- **`main.js`** — metadata for the editor and schema:
1014
+ When you do need one, declare it in **`main.js`** — the single source of truth:
1017
1015
 
1018
1016
  ```js
1019
1017
  export const vars = {
1020
- 'radius': { default: '0.5rem', description: 'Default border radius for cards and buttons' },
1021
1018
  'radius-lg': { default: '1rem', description: 'Large border radius' },
1022
1019
  'section-padding-y': { default: 'clamp(4rem, 6vw, 7rem)', description: 'Vertical section padding' },
1023
1020
  }
1024
1021
  ```
1025
1022
 
1026
- **`styles.css`** the actual CSS that ships with the foundation:
1023
+ Each entry does everything at once: it ships the default as a CSS custom property (`--radius-lg`, `--section-padding-y`) so `var(--section-padding-y)` resolves everywhere, it gives the visual editor a description and type, and it's the value a site overrides in `theme.yml` under `vars:` (the site's theme CSS wins). You don't declare these anywhere else — the defaults reach the browser on their own, in dev and in production, whether the foundation is bundled or loaded at runtime.
1027
1024
 
1028
- ```css
1029
- @theme inline {
1030
- --radius: 0.5rem;
1031
- --radius-lg: 1rem;
1032
- --section-padding-y: clamp(4rem, 6vw, 7rem);
1033
- }
1034
- ```
1025
+ A `styles.css` `@theme` block is a separate tool for a different job: registering a token so **Tailwind generates utility classes** from it (`@theme { --breakpoint-xs: 30rem }` → `xs:` variants). Reach for it to extend Tailwind's vocabulary — not to ship a plain default.
1035
1026
 
1036
- The `styles.css` declaration ensures defaults are present in the foundation's CSS output and enables Tailwind shorthand (`rounded-(--radius)` instead of `rounded-[var(--radius)]`). The `main.js` declaration provides descriptions and types for the visual editor. Sites override values in `theme.yml` under `vars:`the site's theme CSS takes priority over the foundation defaults.
1027
+ **A name that matches a Tailwind namespace is an intentional override.** A var named after a Tailwind v4 token scale — `radius-*`, `shadow-*`, `spacing`, `font-*` — redefines that scale wherever the matching utility appears: declaring `radius-lg` retunes every `rounded-lg` in the foundation from Tailwind's default to your value (sites can still override in `theme.yml`). That's the point when you mean it just name deliberately so you don't reshape a utility by accident.
1037
1028
 
1038
1029
  **Common mistake:** Using foundation vars for values that belong to a specific component. A header height is a layout param, not a foundation var — the layout component owns it. A sidebar width is a layout param too. Foundation vars are for values that multiple unrelated components share — radii, spacing, shadows.
1039
1030
 
@@ -1,9 +1,9 @@
1
1
  {
2
2
  "schemaVersion": 1,
3
- "generatedAt": "2026-07-02T17:25:26.338Z",
3
+ "generatedAt": "2026-07-13T17:29:11.603Z",
4
4
  "packages": {
5
5
  "@uniweb/build": {
6
- "version": "0.14.21",
6
+ "version": "0.14.23",
7
7
  "path": "framework/build",
8
8
  "deps": [
9
9
  "@uniweb/content-reader",
@@ -25,7 +25,7 @@
25
25
  "deps": []
26
26
  },
27
27
  "@uniweb/core": {
28
- "version": "0.7.14",
28
+ "version": "0.7.16",
29
29
  "path": "framework/core",
30
30
  "deps": [
31
31
  "@uniweb/semantic-parser",
@@ -43,7 +43,7 @@
43
43
  "deps": []
44
44
  },
45
45
  "@uniweb/kit": {
46
- "version": "0.9.18",
46
+ "version": "0.9.20",
47
47
  "path": "framework/kit",
48
48
  "deps": [
49
49
  "@uniweb/core",
@@ -61,7 +61,7 @@
61
61
  "deps": []
62
62
  },
63
63
  "@uniweb/runtime": {
64
- "version": "0.8.20",
64
+ "version": "0.8.22",
65
65
  "path": "framework/runtime",
66
66
  "deps": [
67
67
  "@uniweb/core",
@@ -89,17 +89,17 @@
89
89
  "deps": []
90
90
  },
91
91
  "@uniweb/templates": {
92
- "version": "0.7.41",
92
+ "version": "0.7.42",
93
93
  "path": "framework/templates",
94
94
  "deps": []
95
95
  },
96
96
  "@uniweb/theming": {
97
- "version": "0.1.4",
97
+ "version": "0.1.5",
98
98
  "path": "framework/theming",
99
99
  "deps": []
100
100
  },
101
101
  "@uniweb/unipress": {
102
- "version": "0.4.28",
102
+ "version": "0.4.30",
103
103
  "path": "framework/unipress",
104
104
  "deps": [
105
105
  "@uniweb/build",