uniweb 0.10.1 → 0.10.4

package/README.md

@@ -257,7 +257,7 @@ You can delete the `foundation/` folder entirely and point your site at a publis
 
 _Site-first_ — You're building a website. The foundation is your component library, co-developed with the site. This is the common case.
 
-_Foundation-first_ — You're building a component system. The site is a test harness with sample content. The real sites live elsewhere—other repositories, other teams, or managed on [uniweb.app](https://uniweb.app). Use `uniweb add site` to add multiple test sites exercising a shared foundation.
+_Foundation-first_ — You're building a component system. The site is a test harness with sample content. The real sites live elsewhere—other repositories, other teams, or managed on [hub.uniweb.app](https://hub.uniweb.app). Use `uniweb add site` to add multiple test sites exercising a shared foundation.
 
 ## Growing Your Project
 
@@ -299,11 +299,11 @@ The structure you start with scales without rewrites:
 
 1. **Single project** — One site, one foundation. Develop and deploy together. Most projects stay here.
 
-2. **Published foundation** — Release your foundation as an npm package or to [uniweb.app](https://uniweb.app). Other sites can use it without copying code.
+2. **Published foundation** — Release your foundation as an npm package or to [hub.uniweb.app](https://hub.uniweb.app). Other sites can use it without copying code.
 
 3. **Multiple sites** — Several sites share one foundation. Update components once, every site benefits.
 
-4. **Platform-managed sites** — Sites built on [uniweb.app](https://uniweb.app) with visual editing tools can use your foundation. You develop components locally; content teams work in the browser.
+4. **Platform-managed sites** — Sites built on [hub.uniweb.app](https://hub.uniweb.app) with visual editing tools can use your foundation. You develop components locally; content teams work in the browser.
 
 Start with local files deployed anywhere. The same foundation works across all these scenarios.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.10.1",
+  "version": "0.10.4",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,14 +41,14 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/kit": "0.9.0",
-    "@uniweb/runtime": "0.8.1",
-    "@uniweb/core": "0.7.0"
+    "@uniweb/runtime": "0.8.3",
+    "@uniweb/kit": "0.9.2",
+    "@uniweb/core": "0.7.2"
   },
   "peerDependencies": {
-    "@uniweb/build": "0.10.1",
+    "@uniweb/build": "0.10.3",
     "@uniweb/content-reader": "1.1.4",
-    "@uniweb/semantic-parser": "1.1.9"
+    "@uniweb/semantic-parser": "1.1.10"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -891,7 +891,7 @@ fetch:
   limit: 3
 ```
 
-**Lean lists with `deferred:`.** Collections with heavy fields (article bodies, large nested arrays) can declare `deferred: [body]` in `site.yml`. The cascade payload omits those fields; per-record full files are emitted at `/data/<name>/<slug>.json`. On dynamic-route pages the focused entity's full record is delivered automatically; elsewhere components fetch on demand via the `useEntityDetail` kit hook.
+**Lean lists with `deferred:`.** Collections with heavy fields (article bodies, large nested arrays) can declare `deferred: [body]` in `site.yml`. The cascade payload omits those fields; per-record full files are emitted at `/data/<name>/<slug>.json` (file-based collections — markdown, YAML, or JSON) or fetched from an author-declared `detailUrl:` pattern (API-backed collections). On dynamic-route pages the focused entity's full record is delivered automatically; elsewhere components fetch on demand via the `useEntityDetail` kit hook.
 
 **Component-side fetching.** When a component genuinely needs to fetch something on its own (a search box, a "load more" button, a popover that lazy-loads), use the kit hooks (`useFetched`, `useCacheEntry`, `useEntityDetail`). They share the framework's cache and dispatcher with declarative fetches; same-key requests dedupe automatically.
 

package/src/commands/build.js

@@ -11,9 +11,10 @@
  */
 
 import { existsSync, readFileSync } from 'node:fs'
-import { resolve, join } from 'node:path'
+import { resolve, join, dirname } from 'node:path'
 import { spawn } from 'node:child_process'
 import { writeFile, mkdir } from 'node:fs/promises'
+import { createRequire } from 'node:module'
 
 // Import build utilities from @uniweb/build
 import {
@@ -123,6 +124,46 @@ function runCommand(command, args, cwd) {
   })
 }
 
+/**
+ * Resolve the project's local Vite binary.
+ *
+ * We intentionally do NOT fall back to `npx vite`: npx resolves through npm's
+ * global cache, which may hold a stale Vite version (e.g. Vite 5 ignores
+ * lib.fileName for CSS and always emits style.css). Using the project's local
+ * Vite guarantees the version declared in package.json is the one that runs.
+ *
+ * @param {string} projectDir
+ * @returns {string} Absolute path to the vite CLI entry
+ */
+function resolveLocalVite(projectDir) {
+  const require = createRequire(join(projectDir, 'package.json'))
+  let pkgJsonPath
+  try {
+    pkgJsonPath = require.resolve('vite/package.json')
+  } catch {
+    throw new Error(
+      `Vite is not installed in ${projectDir}.\n` +
+      `Run \`pnpm install\` (or npm/yarn install) in the project before building.`
+    )
+  }
+  const pkg = JSON.parse(readFileSync(pkgJsonPath, 'utf8'))
+  const binRel = typeof pkg.bin === 'string' ? pkg.bin : pkg.bin?.vite
+  if (!binRel) {
+    throw new Error(`Could not find vite bin entry in ${pkgJsonPath}`)
+  }
+  return join(dirname(pkgJsonPath), binRel)
+}
+
+/**
+ * Run the project's local Vite with the given args.
+ * @param {string} projectDir
+ * @param {string[]} args - e.g. ['build']
+ */
+async function runLocalVite(projectDir, args) {
+  const viteBin = resolveLocalVite(projectDir)
+  await runCommand(process.execPath, [viteBin, ...args], projectDir)
+}
+
 /**
  * Build a foundation
  */
@@ -158,7 +199,7 @@ async function buildFoundation(projectDir, options = {}) {
 
   // Check if vite.config.js uses the generated entry
   // For now, just run the standard vite build
-  await runCommand('npx', ['vite', 'build'], projectDir)
+  await runLocalVite(projectDir, ['build'])
 
   // Vite's foundation plugin generates dist/meta/schema.json
   // and processes preview images during the build.
@@ -351,7 +392,7 @@ async function buildSite(projectDir, options = {}) {
   info('Building site...')
 
   // Run vite build for sites
-  await runCommand('npx', ['vite', 'build'], projectDir)
+  await runLocalVite(projectDir, ['build'])
 
   success('Site build complete')
 

package/src/commands/handoff.js

@@ -160,7 +160,7 @@ function showWebHandoff(email, name) {
   console.log('')
   info(`Web-based handoff`)
   console.log('')
-  console.log(`  1. Create a site on ${colors.cyan}uniweb.app${colors.reset} using ${colors.bright}${name}${colors.reset}`)
+  console.log(`  1. Create a site on ${colors.cyan}hub.uniweb.app${colors.reset} using ${colors.bright}${name}${colors.reset}`)
   console.log(`  2. Add pages and content`)
   console.log(`  3. Transfer ownership to ${colors.bright}${email}${colors.reset}:`)
   console.log(`     ${colors.dim}Settings → Transfer site${colors.reset}`)

package/src/commands/invite.js

@@ -275,10 +275,10 @@ async function handleCreate(args, email) {
     console.log('')
     if (isExtension) {
       console.log(`  ${colors.dim}When ${invite.email} adds ${name} to their site${colors.reset}`)
-      console.log(`  ${colors.dim}on uniweb.app or Studio, it will be authorized automatically.${colors.reset}`)
+      console.log(`  ${colors.dim}on hub.uniweb.app or Studio, it will be authorized automatically.${colors.reset}`)
     } else {
       console.log(`  ${colors.dim}When ${invite.email} creates a site with ${name}${colors.reset}`)
-      console.log(`  ${colors.dim}on uniweb.app or Studio, it will be authorized automatically.${colors.reset}`)
+      console.log(`  ${colors.dim}on hub.uniweb.app or Studio, it will be authorized automatically.${colors.reset}`)
     }
   } catch (err) {
     error(err.message)

package/src/framework-index.json

@@ -1,9 +1,9 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-04-19T02:30:04.354Z",
+  "generatedAt": "2026-04-23T17:16:28.977Z",
   "packages": {
     "@uniweb/build": {
-      "version": "0.10.1",
+      "version": "0.10.3",
       "path": "framework/build",
       "deps": [
         "@uniweb/content-reader",
@@ -24,7 +24,7 @@
       "deps": []
     },
     "@uniweb/core": {
-      "version": "0.7.0",
+      "version": "0.7.2",
       "path": "framework/core",
       "deps": [
         "@uniweb/semantic-parser",
@@ -42,7 +42,7 @@
       "deps": []
     },
     "@uniweb/kit": {
-      "version": "0.9.0",
+      "version": "0.9.2",
       "path": "framework/kit",
       "deps": [
         "@uniweb/core"
@@ -54,12 +54,12 @@
       "deps": []
     },
     "@uniweb/press": {
-      "version": "0.2.8",
+      "version": "0.3.1",
       "path": "framework/press",
       "deps": []
     },
     "@uniweb/runtime": {
-      "version": "0.8.1",
+      "version": "0.8.3",
       "path": "framework/runtime",
       "deps": [
         "@uniweb/core",
@@ -77,12 +77,12 @@
       "deps": []
     },
     "@uniweb/semantic-parser": {
-      "version": "1.1.9",
+      "version": "1.1.10",
       "path": "framework/semantic-parser",
       "deps": []
     },
     "@uniweb/templates": {
-      "version": "0.7.32",
+      "version": "0.7.34",
       "path": "framework/templates",
       "deps": []
     },

package/src/utils/config.js

@@ -15,7 +15,7 @@ import { filterCmd } from './pm.js'
 // ── Platform URLs ──────────────────────────────────────────────
 
 // Production defaults — regular users get these out of the box
-const PRODUCTION_BACKEND_URL = 'https://uniweb.app'
+const PRODUCTION_BACKEND_URL = 'https://hub.uniweb.app'
 const PRODUCTION_REGISTRY_URL = 'https://site-router.uniweb-edge.workers.dev'
 
 /**