@uniweb/build 0.47.0 → 0.47.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "0.47.0",
+  "version": "0.47.1",
   "description": "Build tooling for the Uniweb Component Web Platform",
   "type": "module",
   "exports": {
@@ -65,7 +65,7 @@
     "@uniweb/schemas": "^0.2.13"
   },
   "optionalDependencies": {
-    "@uniweb/runtime": "^0.20.3"
+    "@uniweb/runtime": "^0.21.0"
   },
   "peerDependencies": {
     "vite": "^5.0.0 || ^6.0.0 || ^7.0.0",
@@ -74,7 +74,7 @@
     "@tailwindcss/vite": "^4.0.0",
     "@vitejs/plugin-react": "^4.0.0 || ^5.0.0",
     "vite-plugin-svgr": "^4.0.0",
-    "@uniweb/core": "^0.26.1"
+    "@uniweb/core": "^0.26.2"
   },
   "peerDependenciesMeta": {
     "vite": {

package/src/hosts/generic-static.js

@@ -7,9 +7,14 @@
  * indexes natively).
  *
  * Selecting `host: generic-static` explicitly opts out of the Netlify
- * `_redirects` output. Pages with `redirect:` or `rewrite:` directives
- * still emit their meta-refresh HTML (handled inside prerender.js), so
- * those keep working without host help.
+ * `_redirects` output. A page with `redirect:` still emits its
+ * meta-refresh HTML (handled inside prerender.js), so redirects keep
+ * working without host help.
+ *
+ * ⛔ **`rewrite:` does NOT — this comment used to claim it did.** A rewrite
+ * is a proxy: the URL stays and the body comes from an upstream, which no
+ * static host can do. Prerender writes nothing for such a page, so the
+ * route is absent rather than degraded.
  */
 
 const adapter = {

package/src/hosts/github-pages.js

@@ -13,9 +13,15 @@
  * postBuild: writes `dist/.nojekyll` (empty file).
  *
  * GitHub Pages does not consume `_redirects` (that's a
- * Cloudflare/Netlify thing) — page-level redirects go through the
- * meta-refresh HTML the prerender already emits for `redirect:` /
- * `rewrite:` directives.
+ * Cloudflare/Netlify thing) — a page's `redirect:` goes through the
+ * meta-refresh HTML the prerender emits for it.
+ *
+ * ⛔ **`rewrite:` DOES NOT WORK HERE, and this comment used to say it did.**
+ * A rewrite is a PROXY — the path keeps its URL and is served from an
+ * upstream (`/proxied/* https://upstream/:splat 200` on a host that has a
+ * redirects layer). That needs a server. Prerender deliberately writes
+ * nothing for a `rewrite:` page, so on this host the route is simply
+ * absent. Use `redirect:` if a visible URL change is acceptable.
  *
  * Two ways to publish, both supported:
  *

package/src/prerender.js

@@ -981,9 +981,14 @@ export async function prerenderSite(siteDir, options = {}) {
         continue
       }
 
-      // Rewrite pages: served by an external site, skip rendering entirely
+      // Rewrite pages: served by an external site, skip rendering entirely.
+      // ⛔ NO FILE IS WRITTEN, ON ANY HOST — a rewrite is a PROXY (the URL stays,
+      // the body comes from upstream), so it can only be served by a host with a
+      // redirects layer: `_redirects` spells it `200`, not `302`. Where that layer
+      // does not exist the route is ABSENT, not degraded — so the line says what
+      // did not happen, which is the only signal an author gets here.
       if (page.rewrite) {
-        onProgress(`  Rewrite ${outputRoute} → ${page.rewrite}`)
+        onProgress(`  Rewrite ${outputRoute} → ${page.rewrite} (no page emitted — needs a host that proxies)`)
         continue
       }