uniweb 1.24.9 → 1.24.10

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": "1.24.9",
3
+ "version": "1.24.10",
4
4
  "description": "Create structured Vite + React sites with content/code separation",
5
5
  "type": "module",
6
6
  "bin": {
@@ -41,15 +41,15 @@
41
41
  "js-yaml": "^4.3.2",
42
42
  "prompts": "^2.4.2",
43
43
  "tar": "^7.5.21",
44
+ "@uniweb/core": "~1.5.1",
44
45
  "@uniweb/content-writer": "~1.3.1",
45
46
  "@uniweb/schemas": "~1.6.7",
46
- "@uniweb/core": "~1.5.1",
47
47
  "@uniweb/semantic-parser": "~1.13.0"
48
48
  },
49
49
  "peerDependencies": {
50
- "@uniweb/build": "~1.13.5",
51
50
  "@uniweb/content-reader": "~1.5.7",
52
- "@uniweb/semantic-parser": "~1.13.0"
51
+ "@uniweb/semantic-parser": "~1.13.0",
52
+ "@uniweb/build": "~1.13.5"
53
53
  },
54
54
  "peerDependenciesMeta": {
55
55
  "@uniweb/build": {
@@ -1619,7 +1619,7 @@ Semantic tokens come from `theme-tokens.css` (populated from `theme.yml`). Use `
1619
1619
 
1620
1620
  These compose with tokens — they adapt per context because they reference token variables — while adding nuance the token set doesn't provide. Use palette shades directly (`var(--primary-300)`, `bg-neutral-200`) for fine-grained control. **The priority: design quality > portability > configurability.** A beautiful foundation for one site is worth more than a generic one that looks flat.
1621
1621
 
1622
- Three lines a ported design will try to bring with it, each of which breaks something:
1622
+ Four things a ported design will try to bring with it, each of which breaks something:
1623
1623
 
1624
1624
  > **Don't set `scroll-behavior: smooth` globally.** The runtime owns scrolling: it already smooth-scrolls anchor targets itself (`scrollIntoView({ behavior: 'smooth' })`), so the CSS adds nothing there — but it resets and restores scroll on route changes with the two-argument `scrollTo(x, y)`, which *inherits* the property. Route changes then animate their scroll-to-top, and back-button restoration (which scrolls, checks the position on the next frame, and retries) keeps interrupting its own animation. Scope it to a specific scrollable element if you need it; never to `html` or `body`.
1625
1625
 
@@ -1627,6 +1627,8 @@ Three lines a ported design will try to bring with it, each of which breaks some
1627
1627
 
1628
1628
  > **Font smoothing is a per-scheme decision, not a reset.** `-webkit-font-smoothing: antialiased` (macOS only) forces grayscale rasterization, which thins strokes. On dark surfaces that usefully counteracts the bloom of light text on near-black; on light surfaces it costs contrast and makes body text spindly. Scope it — `.scheme-dark { -webkit-font-smoothing: antialiased; -moz-osx-font-smoothing: grayscale; }` — rather than putting it on `html`.
1629
1629
 
1630
+ > **Write an entrance animation in CSS, not in JavaScript.** A CSS animation on a prerendered page starts at first paint and carries on when the browser renders over that page, so a hero fades in once. One a component starts when it mounts (a motion library, a `useEffect`) can only start when the page boots. Until then the visitor sees its first frame, which for a fade is nothing, or the finished section, which then animates in. `uniweb dev` does not prerender, so only a built site shows this.
1631
+
1630
1632
  ### Composition: items, child sections, insets
1631
1633
 
1632
1634
  Pages are sequences of sections — the obvious layer. The framework also supports real nesting, without leaving markdown.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "schemaVersion": 1,
3
- "generatedAt": "2026-10-31T14:53:03.601Z",
3
+ "generatedAt": "2026-10-31T15:45:04.675Z",
4
4
  "packages": {
5
5
  "@uniweb/api": {
6
6
  "version": "1.6.7"
@@ -36,7 +36,7 @@
36
36
  "version": "1.2.8"
37
37
  },
38
38
  "@uniweb/runtime": {
39
- "version": "1.3.3"
39
+ "version": "1.3.4"
40
40
  },
41
41
  "@uniweb/scene": {
42
42
  "version": "1.0.1"