uniweb 1.25.5 → 1.25.6

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.25.5",
3
+ "version": "1.25.6",
4
4
  "description": "Create structured Vite + React sites with content/code separation",
5
5
  "type": "module",
6
6
  "bin": {
@@ -42,14 +42,14 @@
42
42
  "prompts": "^2.4.2",
43
43
  "tar": "^7.5.21",
44
44
  "@uniweb/core": "~1.6.1",
45
- "@uniweb/schemas": "~1.6.7",
46
45
  "@uniweb/semantic-parser": "~1.13.2",
46
+ "@uniweb/schemas": "~1.6.7",
47
47
  "@uniweb/content-writer": "~1.3.1"
48
48
  },
49
49
  "peerDependencies": {
50
- "@uniweb/build": "~1.14.2",
51
- "@uniweb/content-reader": "~1.5.8",
52
- "@uniweb/semantic-parser": "~1.13.2"
50
+ "@uniweb/build": "~1.14.3",
51
+ "@uniweb/semantic-parser": "~1.13.2",
52
+ "@uniweb/content-reader": "~1.5.8"
53
53
  },
54
54
  "peerDependenciesMeta": {
55
55
  "@uniweb/build": {
@@ -81,7 +81,7 @@ When a rule in §2 feels like friction, that is the moment you are about to take
81
81
  | `records/blog/2025/post.md`; one YAML file holding a list | Flat: `records/<schema>/<name>.md`, one record per file; the file name is `$name`. | folder read as a schema, silent |
82
82
  | `` `/blog/${slug}` `` | `item.$route` — never compose a URL. | works until a page moves |
83
83
  | `page.yml` in a folder of pages | It makes one page, each `.md` a section. `folder.yml` keeps them pages and carries `layout`, `title` and SEO. Over a mount, `page.yml` with markdown of its own is a landing page *above* the mounted pages; a mount is one level under `pages/`, and a local subfolder beside it isn't read. | silent; the build names that subfolder |
84
- | Paste the gtag / GTM / Meta pixel snippet into a component, `index.html`, or `services.tracking.scripts` | Static build (`export`, `deploy --host`): the snippet in `head.html` beside `site.yml`. Uniweb Cloud (`publish`): `services.google: { id: G-… }` — `head.html` isn't applied there, and `scripts` takes URLs only, so GA sends nothing. | silent — GA reports nothing |
84
+ | Paste the gtag / GTM / Meta pixel snippet into a component, `index.html`, or `services.tracking.scripts` | Uniweb Cloud (`publish`): `services.google: { id: G-… }`, or `GTM-…` for a container, and the host loads Google's tag, free, with no code, on any foundation. `head.html` isn't applied there, and `scripts` takes URLs only. Static build (`export`, `deploy --host`): the snippet in `head.html` beside `site.yml`. More: `uniweb guide services`. | silent — Google reports nothing |
85
85
  | Expect `{company}` to resolve | Only under a foundation with `createLoomHandlers`; otherwise it renders literally. | build warns if `site.yml` has `placeholders:` |
86
86
  | `hidden: true` on `pages/404/` to keep it out of nav | That makes it a draft. `hideIn: ['*']` controls nav. | silent |
87
87
  | Treat `@child.md` / `_draft.md` as names | `@` = child section, placed by `nest:` (with none it renders last; a `sections:` list drops it); `_` = ignored. | build warns, unless `sections:` dropped it |
@@ -323,7 +323,7 @@ Every guide ships with the CLI this project pins, so it describes the version in
323
323
  | change colors, fonts, light/dark, tokens, `styles.css` | `uniweb guide theme` |
324
324
  | start a project, grow the workspace, learn from a template | `uniweb guide start` |
325
325
  | work with records, queries, `[slug]` pages, external APIs, schemas, Loom | `uniweb guide data` |
326
- | add search, forms, tracking, an assistant | `uniweb guide services` |
326
+ | add search, forms, tracking, Google Analytics or Tag Manager, an assistant | `uniweb guide services` |
327
327
  | the site has accounts or member data (`services.backend`, `@uniweb/api`) | `uniweb guide backend` |
328
328
  | add a language | `uniweb guide i18n` |
329
329
  | publish, deploy, push/pull, register, CI, workspaces, updates | `uniweb guide ship` |
@@ -127,7 +127,7 @@ Short codes: `lu` Lucide, `hi`/`hi2` Heroicons v1/v2, `fi` Feather, `pi` Phospho
127
127
  ![alt](./img.jpg){href=/products} clickable media: href + target ride along
128
128
  ```
129
129
 
130
- Image attributes: `{width=800 height=600 loading=lazy fit=cover position=center author="Jane Doe"}`. Video: `{poster=./thumb.jpg autoplay muted loop controls}` — name a poster; a static build makes one only when none is named and ffmpeg is installed, and `uniweb publish` sends only a named poster. A `{role=pdf}` document adds `{preview=./cover.jpg author=… description=…}` and arrives as `{ url, name, mime, size?, alt, caption, … }`.
130
+ Image attributes: `{width=800 height=600 loading=lazy fit=cover position=center author="Jane Doe"}`. `width` and `height` hold an image's place on the page while its file loads, so what's under it doesn't jump when it arrives; use the file's own size, and a stylesheet still scales it. A static build fills them in for a local file when you give neither. On a site a backend hosts, write them on an image in the flow. In a PDF, only a width with a unit (`50%`, `10cm`) sizes an image. Video: `{poster=./thumb.jpg autoplay muted loop controls}` — name a poster; a static build makes one only when none is named and ffmpeg is installed, and `uniweb publish` sends only a named poster. A `{role=pdf}` document adds `{preview=./cover.jpg author=… description=…}` and arrives as `{ url, name, mime, size?, alt, caption, … }`.
131
131
 
132
132
  **Section links:** `page:about#team` → `/about#section-team`; `page:/#features` → a homepage section. The id is the file name without its number (`2-features.md` → `features`) or `id:` in frontmatter.
133
133
 
@@ -162,6 +162,8 @@ Three uses by info string: `yaml:`/`json:` data (parsed into `content.data.tag`,
162
162
 
163
163
  Two tags, not a tag plus a variant: a warning and a note are `md:warning` and `md:note`. The fence takes no params.
164
164
 
165
+ A ` ```mermaid ` fence is a snippet that a foundation can draw as a diagram, with kit's `Mermaid` (foundation guide). Where it doesn't, or the diagram has a syntax error, the page shows it as code. Check by looking at the page: the build says nothing either way. ` ```mermaid:flow ` keeps the text at `content.data.flow`, for a section that declares `flow` and draws it.
166
+
165
167
  ### Math
166
168
 
167
169
  LaTeX compiles to MathML Core at build time — no runtime library. `$x^2$` inline; `$$x^2$$` display (block on its own line, inline display mid-paragraph); a ` ```math ` fence for multi-line; `\$` for a literal dollar. A `$…$` span is math only when no whitespace touches the delimiters *and* the closing `$` isn't followed by a digit — so `$5 and $10` stays prose and `Let $f(x) = 5$ be` is math. Math survives prerender, epub/pagedjs output and the editor. Display math lands in `content.math`, and inline math stays in its paragraph. A foundation that draws equations imports `@uniweb/kit/math-tokens.css` (theme guide).
@@ -24,6 +24,22 @@ import { Section, Prose, Article } from '@uniweb/kit'
24
24
 
25
25
  `Prose` renders headings, paragraphs, images, snippets, lists with prose typography. Markdown footnotes (`[^1]` and a `[^1]: the note` paragraph in the same file) become numbered links with the notes listed at the end; a section drawing `content.paragraphs` itself sees them as the text they are. Tagged data blocks are skipped (read them from `content.data`). It also works as a typography wrapper: `<Prose>{children}</Prose>`. `Article` is `Prose` in a semantic `<article>`.
26
26
 
27
+ **Drawing an element your own way.** `components` on `Prose`, `Render`, `Article` or `Section` replaces how one element type is drawn, and kit keeps the rest. An entry receives `{ element, block, children }`: a `codeBlock` has `element.text` and `element.attrs.language`, a `dataBlock` (a tagged fence, drawn where the author put it) has `element.tag` and `element.data`, and a `concept_block` has `element.tag` and `children`. To use it across sections, wrap `Prose` once in a component of your own.
28
+
29
+ ```jsx
30
+ import { Prose, Code, Mermaid } from '@uniweb/kit'
31
+
32
+ function CodeBlock({ element: { text, attrs } }) {
33
+ return attrs?.language === 'mermaid'
34
+ ? <Mermaid source={text} />
35
+ : <Code content={text} language={attrs?.language} />
36
+ }
37
+
38
+ <Prose content={content} block={block} components={{ codeBlock: CodeBlock }} />
39
+ ```
40
+
41
+ **Diagrams.** `Mermaid` draws a ` ```mermaid ` fence, and only where a foundation passes it one like this: elsewhere the fence stays code. The prerendered page holds the source as code, and the diagram replaces it when it comes near the view, so expect the page to move by the difference in height. Its colors come from the section's tokens. It's an image, drawn by an engine in a sandboxed frame loaded from a CDN, so its nodes can't be clicked, its text can't be selected, and its labels use the system font. A foundation that doesn't import it carries none of it.
42
+
27
43
  **Prose styling.** `<Prose>` and any container you put `<Render>` output in use kit's `prose` classes, supplied by one import in `styles.css`:
28
44
 
29
45
  ```css
@@ -47,7 +63,7 @@ Skip it and prose is unstyled (lists lose bullets) while the markup looks right;
47
63
  **Data fetching:** `useFetched`, `useCacheEntry`, `useWholeRecord`
48
64
  **Forms:** `useFormValues`, `valueAt`, `useFormSubmit`, `submitForm`, `resolveSubmitTarget` (services guide)
49
65
  **Utilities:** `cn()`, `SafeHtml`, `SocialIcon`, `filterSocialLinks(links)`, `getSocialPlatform(url)`, `getLocaleLabel(locale)`
50
- **Other styled:** `Code`, `Alert`, `Table`, `Details`, `Divider`, `Disclaimer`
66
+ **Other styled:** `Code`, `Mermaid`, `Alert`, `Table`, `Details`, `Divider`, `Disclaimer`
51
67
 
52
68
  Things you won't discover from exports:
53
69
 
@@ -100,7 +116,7 @@ export default {
100
116
 
101
117
  **`content:`** names what the component reads, each as an author label with optional count: `title`, `pretitle`, `subtitle`, `paragraphs`, `links`, `lists`, `items`, `media`, `icons`, `documents`, `snippets`, `tables`, `math`, `quotes`, `sequence`. It is a description for the editor and for other agents, not a validation schema. Take what you expect — `content.paragraphs[0]` if you need one paragraph — and render every paragraph or every item only when showing them all is the point. A section may hold content the type never reads; don't enumerate it, validate it or react to it.
102
118
 
103
- - **`media`** is an image, a video, or an embedded component. `media: { label, types: ['image'] }` narrows it; `image:`, `videos:`, `insets:` are the same slot narrowed to one type. Read `content.media` (author's order, each with `kind`) and render with `<Visual media={content.media} block={block} />`. `<Image>` would drop a diagram placed there; `<Media>` is a video player.
119
+ - **`media`** is an image, a video, or an embedded component. `media: { label, types: ['image'] }` narrows it; `image:`, `videos:`, `insets:` are the same slot narrowed to one type. Read `content.media` (author's order, each with `kind`) and render with `<Visual media={content.media} block={block} />`. `<Image>` would drop a diagram placed there; `<Media>` is a video player. An image's `width` and `height`, when it has them, reach the `<img>` as attributes, so a class that sets only its height needs `w-auto` too (`h-8 w-auto`), or the width stays the file's.
104
120
  - **`sequence`** says the component renders the whole section as written. `{ label, except: ['table', 'math'] }` names kinds it leaves out; `placement` the placements it lays out — `true` (all four, what `<Render>`/`<Prose>`/`<Article>` do), a list, or a map per kind. An editor offers an author only those.
105
121
  - **`items: { label, content: {…} }`** says what each entry holds.
106
122
 
@@ -316,6 +332,8 @@ Content-less containers appear as group nodes (`hasContent: false`); link with `
316
332
 
317
333
  ## Packaging
318
334
 
335
+ **A heavy library used on demand.** `import('some-package')` where you use it keeps the package out of the page's first load and out of `dist/entry-ssr.js`, the file a host loads to render a page. A dynamic import of your own module only splits the browser's load: `entry-ssr.js` folds that module in, with every package it imports statically, and runs them when the file loads. So put the `import()` on the package, not on a component of yours that imports it. The build is green either way; the size of `entry-ssr.js` shows which you have.
336
+
319
337
  **`package.json` `uniweb` block** (all optional): `runtimePolicy` — a statement of how far past the recorded runtime version a host may move a site. The foundation's name and scope are `name` in `main.js` (`'@acme/marketing'`), not here; a name with no scope is unregistered, and the first `uniweb register` writes the scope in (from `--scope` or the Uniweb workspace you are logged in to). A foundation's own schemas register under the same scope (`@/article` → `@acme/article`). `uniweb.supports` is covered in the services guide.
320
338
 
321
339
  **Runtime floor.** Your code externalizes `react`, `react-dom`, both JSX runtimes and `@uniweb/core`; the runtime supplies them. At build time the foundation records the `@uniweb/runtime` version it linked against into `dist/runtime-pin.json`, and `uniweb register` sends that version as its floor. `{ "uniweb": { "runtimePolicy": "exact" } }` asks for no movement past it, for a foundation that reaches into undocumented internals: it is recorded in that file and not sent at register, so whether anything acts on it is the host's to say. `@uniweb/runtime` arrives transitively through `@uniweb/build`; don't add it to the foundation's dependencies — bump `@uniweb/build` instead.
@@ -27,7 +27,7 @@
27
27
  {
28
28
  "name": "services",
29
29
  "title": "Services",
30
- "description": "add search, forms, tracking, an assistant"
30
+ "description": "add search, forms, tracking, Google Analytics or Tag Manager, an assistant"
31
31
  },
32
32
  {
33
33
  "name": "backend",
@@ -109,7 +109,7 @@ The endpoint must accept the framework's batched `{ "events": [ … ] }` POST (`
109
109
  **A `scripts` entry is a URL and nothing else, so these can't be installed that way.** Each one's install runs inline lines; from a URL alone GA sends nothing and Tag Manager never gets its page-load event. A tag carrying an attribute the vendor reads (`data-domain`, `data-website-id`) has the same problem. What works depends on who builds the pages:
110
110
 
111
111
  - **The framework builds them** (`uniweb export`, `uniweb deploy --host=<adapter>`): the vendor's snippet goes in `head.html` next to `site.yml`, and the build adds it to every page's `<head>`. A `services.google` entry does nothing here.
112
- - **Uniweb Cloud builds them** (`uniweb publish`): `head.html` is kept and synced but **not applied**. For Google's two, name the ID and the host loads the tag from the next publish, with no code, on any foundation:
112
+ - **Uniweb Cloud builds them** (`uniweb publish`): `head.html` is kept and synced but **not applied**. For Google's two, name the ID and the host loads the tag from the next publish, free, with no code, on any foundation:
113
113
 
114
114
  ```yaml
115
115
  services:
@@ -117,7 +117,7 @@ The endpoint must accept the framework's batched `{ "events": [ … ] }` POST (`
117
117
  id: G-XXXXXXXXXX # or GTM-XXXXXXX, or a list of both
118
118
  ```
119
119
 
120
- The app's site settings edit the same entry; a pull or push carries a change across. Leave `services.tracking.scripts` unset beside it — a site's own list replaces what the host states, so Google's tag would not load. `tracking: { enabled: false, consent: required }` beside it holds the tag until a visitor answers, and needs a component using `useTrackingConsent()`, or it never loads. Gate that component on the hook's `status`: `isTrackingEnabled()` is false here. Any other such vendor has to run from the foundation's code, so a site whose foundation you can't change can't add one — say so rather than writing a `head.html` that does nothing.
120
+ The app's site settings don't offer this yet, so for a site someone edits only in the app, `uniweb clone` it, add the entry and `uniweb publish`. Leave `services.tracking.scripts` unset beside it — a site's own list replaces what the host states, so Google's tag would not load. `tracking: { enabled: false, consent: required }` beside it holds the tag until a visitor answers, and needs a component using `useTrackingConsent()`, or it never loads. Gate that component on the hook's `status`: `isTrackingEnabled()` is false here. Any other such vendor has to run from the foundation's code, so a site whose foundation you can't change can't add one — say so rather than writing a `head.html` that does nothing.
121
121
 
122
122
  Either way, tell the person to check Realtime from a browser that doesn't block trackers: a visit from Brave, say, never reaches Google, which looks like a failed install. Google Analytics counts each page a visitor moves to through the browser-history setting, under Enhanced measurement in the data stream's settings, which a new stream has on.
123
123
 
@@ -164,7 +164,7 @@ Every event carries an opaque `visit` key, generated at page load, in memory onl
164
164
 
165
165
  ## Assistant
166
166
 
167
- The service name is `assistant`; a host that runs an agent typically serves it at `/_agent`. Never write that path:
167
+ The service name is `assistant`; a host that runs an agent typically serves it at `/_agent/chat`. Never write that path:
168
168
 
169
169
  ```jsx
170
170
  const { url } = resolveService(website, 'assistant')
@@ -172,3 +172,5 @@ if (!url) return null // no agent on this site — render nothing or a
172
172
  ```
173
173
 
174
174
  No `url` means the site has no agent — never enabled, or this host runs none. Don't retry it, don't hardcode `/_agent/chat` (on a static host that's a 404 indistinguishable from a broken endpoint), and don't tell the visitor. A live agent that errors mid-conversation is ordinary request failure, handled where you make the request. Knowledge pages that feed an assistant: content guide.
175
+
176
+ In `site.yml`, `assistant: true` asks the host for its agent, and a map asks with options: `system` holds its instructions, and `model` and `maxTokens` are preferences a host may ignore. A map with no address still asks the host, so the address stays the host's to state.
@@ -95,7 +95,7 @@ fonts:
95
95
  faces: [{ family: "Fraunces", src: /fonts/fraunces.woff2, weight: "100 900" }]
96
96
  ```
97
97
 
98
- The build adds preconnect hints, emits `@font-face` + preload, drops unreferenced families; `uniweb push` uploads face files under `public/`. The `code` role owns `--font-code`; Tailwind's `font-mono` reads `--font-mono`, a separate var you declare yourself. A role's face on an element it isn't wired onto — a wordmark in the heading face, say — is `font-family: var(--font-heading)`, or a utility of your own: `@theme inline { --font-display: var(--font-heading); }` in `styles.css`, then `font-display`.
98
+ The build adds preconnect hints, emits `@font-face` + preload, drops unreferenced families; `uniweb push` uploads face files under `public/`. An imported font replaces the fallback when it arrives (`display=swap`, unless the URL says otherwise), which can re-wrap text on a first visit. `display=optional` in the URL keeps the font first drawn for that visit instead, and `faces:` serves the files from the site, preloaded. The `code` role owns `--font-code`; Tailwind's `font-mono` reads `--font-mono`, a separate var you declare yourself. A role's face on an element it isn't wired onto — a wordmark in the heading face, say — is `font-family: var(--font-heading)`, or a utility of your own: `@theme inline { --font-display: var(--font-heading); }` in `styles.css`, then `font-display`.
99
99
 
100
100
  ## styles.css
101
101
 
@@ -6,9 +6,10 @@
6
6
  * CloudFront, etc.). Does NOT upload anywhere — `uniweb deploy --host`
7
7
  * uploads to a third-party host; `uniweb publish` ships to Uniweb hosting.
8
8
  *
9
- * The `dist/` output bundles the runtime + foundation + content into
10
- * concatenated packaging, with a vite-built `index.html` + `entry.js` +
11
- * `assets/`. The user copies it to whatever host they like.
9
+ * The `dist/` output concatenates the runtime and a local foundation into the
10
+ * site's JS (a foundation named by URL stays a URL), with the content beside
11
+ * that JS and never in it: a vite-built `index.html` + `entry.js` + `assets/`.
12
+ * The user copies it to whatever host they like.
12
13
  *
13
14
  * Internally this is `uniweb build --bundle` plus user guidance for the
14
15
  * upload step. The `--link` / `--bundle` flag pair is internal-only
@@ -679,10 +679,10 @@ export async function publish(args = []) {
679
679
  reportSchemalessQueries(probe.schemaless, say)
680
680
  const localAssets = probe.localAssets || []
681
681
 
682
- // 3a. A clone with no `$uuid` is bound to no backend site, so every cached map
683
- // that describes one is stale — including after the documented "clear
684
- // `$uuid` to re-publish as a new site" recovery. Must run BEFORE the create,
685
- // which mints a uuid and would make the clone look bound.
682
+ // 3a. A copy with no site uuid for this backend (`sync.json`) is bound to no site
683
+ // there, so every cached map that describes one is stale. `uniweb forget` clears
684
+ // the maps with the uuid; this catches a uuid gone any other way. Must run BEFORE
685
+ // the create, which mints a uuid and would make the copy look bound.
686
686
  const droppedState = clearRemoteSyncStateIfUnbound(siteDir, client.origin)
687
687
  if (droppedState.length) {
688
688
  say.dim(
@@ -697,7 +697,8 @@ export async function publish(args = []) {
697
697
  // so a repeatedly-failing first publish would burn quota with no recovery
698
698
  // short of support. Creating the site first makes the artifact of a failed
699
699
  // publish an EMPTY SITE instead: it costs nothing to keep and the owner can
700
- // clear it. A no-op once `$uuid` is set, so only a first publish pays.
700
+ // clear it. A no-op once `sync.json` holds this backend's site uuid, so only
701
+ // a first publish pays.
701
702
  //
702
703
  // This ordering is load-bearing, not incidental — the asset plan requires an
703
704
  // owner. A test asserts the create precedes the upload.
@@ -348,11 +348,12 @@ export async function push(args = [], deps = {}) {
348
348
  // ⛔ DROP STALE REMOTE STATE FIRST — this must precede the hash read below, and it
349
349
  // did not until 2026-08-19.
350
350
  //
351
- // The guard itself is right and its docblock names this exact outcome: on a clone
352
- // whose `$uuid` was cleared to re-publish as a new site — WHICH IS OUR OWN
353
- // DOCUMENTED RECOVERY — send-only-changed would "skip every entity whose content
354
- // had not changed since the OLD site's last push, so the NEW site would come up
355
- // missing exactly the content that did not change." It was defeated twice over:
351
+ // The guard itself is right and its docblock names this exact outcome: on a copy
352
+ // whose site uuid went without the maps — which our own guidance to clear `$uuid`
353
+ // led to, until 2026-09-21; `uniweb forget` takes both now — send-only-changed would
354
+ // "skip every entity whose content had not changed since the OLD site's last push,
355
+ // so the NEW site would come up missing exactly the content that did not change."
356
+ // It was defeated twice over:
356
357
  //
357
358
  // · it ran AFTER `readSyncCache`, so the emit still diffed against the old
358
359
  // site's hashes even though the file on disk had just been emptied;
@@ -483,7 +484,8 @@ export async function push(args = [], deps = {}) {
483
484
  if (mediaRefs.length) {
484
485
  // The site has to exist before its bytes do — an upload with no owning
485
486
  // entity is charged and cannot be freed, because freeing means deleting the
486
- // owner. A no-op once `$uuid` is set, so only a never-synced site pays.
487
+ // owner. A no-op once `sync.json` holds this backend's site uuid, so only a
488
+ // never-synced site pays.
487
489
  // ⛔ The PINNED ref, not site.yml's. The create is a THIRD writer of this
488
490
  // value — the emit below stamps it via `injectInfo`, publish passes it here,
489
491
  // and push did neither until 2026-08-19: it sent the authored alias (`src`),
@@ -1,12 +1,12 @@
1
1
  {
2
2
  "schemaVersion": 1,
3
- "generatedAt": "2026-11-02T16:57:17.019Z",
3
+ "generatedAt": "2026-11-02T19:27:56.253Z",
4
4
  "packages": {
5
5
  "@uniweb/api": {
6
6
  "version": "1.6.9"
7
7
  },
8
8
  "@uniweb/build": {
9
- "version": "1.14.2"
9
+ "version": "1.14.3"
10
10
  },
11
11
  "@uniweb/content-reader": {
12
12
  "version": "1.5.8"
@@ -24,19 +24,19 @@
24
24
  "version": "1.0.8"
25
25
  },
26
26
  "@uniweb/kit": {
27
- "version": "1.7.2"
27
+ "version": "1.7.3"
28
28
  },
29
29
  "@uniweb/loom": {
30
30
  "version": "1.1.3"
31
31
  },
32
32
  "@uniweb/press": {
33
- "version": "1.2.1"
33
+ "version": "1.2.2"
34
34
  },
35
35
  "@uniweb/projections": {
36
36
  "version": "1.2.10"
37
37
  },
38
38
  "@uniweb/runtime": {
39
- "version": "1.3.12"
39
+ "version": "1.3.13"
40
40
  },
41
41
  "@uniweb/scene": {
42
42
  "version": "1.0.1"
@@ -54,7 +54,7 @@
54
54
  "version": "1.1.2"
55
55
  },
56
56
  "@uniweb/templates": {
57
- "version": "1.2.2"
57
+ "version": "1.2.3"
58
58
  },
59
59
  "@uniweb/theming": {
60
60
  "version": "1.2.1"