@uniweb/build 0.74.0 → 0.74.1

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.
Files changed (2) hide show
  1. package/package.json +5 -5
  2. package/src/prerender.js +9 -5
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@uniweb/build",
3
- "version": "0.74.0",
3
+ "version": "0.74.1",
4
4
  "description": "Build tooling for the Uniweb Component Web Platform",
5
5
  "type": "module",
6
6
  "exports": {
@@ -57,15 +57,15 @@
57
57
  "js-yaml": "^4.1.0",
58
58
  "sharp": "^0.35.3",
59
59
  "yaml": "^2.5.0",
60
- "@uniweb/content-reader": "^1.2.7",
61
- "@uniweb/projections": "^0.7.11",
60
+ "@uniweb/content-reader": "^1.2.8",
62
61
  "@uniweb/content-writer": "^0.3.4",
62
+ "@uniweb/projections": "^0.7.11",
63
63
  "@uniweb/semantic-parser": "^1.5.1",
64
64
  "@uniweb/schemas": "^0.10.0",
65
65
  "@uniweb/theming": "^0.2.0"
66
66
  },
67
67
  "optionalDependencies": {
68
- "@uniweb/runtime": "^0.28.4"
68
+ "@uniweb/runtime": "^0.28.5"
69
69
  },
70
70
  "peerDependencies": {
71
71
  "vite": "^5.0.0 || ^6.0.0 || ^7.0.0",
@@ -75,7 +75,7 @@
75
75
  "@vitejs/plugin-react": "^4.0.0 || ^5.0.0",
76
76
  "vite-plugin-svgr": "^4.0.0",
77
77
  "@uniweb/core": "^0.35.0",
78
- "@uniweb/runtime": "^0.28.4"
78
+ "@uniweb/runtime": "^0.28.5"
79
79
  },
80
80
  "peerDependenciesMeta": {
81
81
  "vite": {
package/src/prerender.js CHANGED
@@ -1098,12 +1098,16 @@ export async function prerenderSite(siteDir, options = {}) {
1098
1098
  continue
1099
1099
  }
1100
1100
 
1101
- // ⛔ `notFound` cannot happen here — this loop iterates pages it already has,
1102
- // so `render` never resolves. Handled anyway: silently writing nothing for a
1103
- // page the loop selected would be the same shape of empty-success bug that
1104
- // `renderPage`'s content-not-loaded guard exists to catch.
1101
+ // `notFound` means the URL names nothing, and there is no page to write for it:
1102
+ // written, a not-found page would be published as a real one. Two cases, said
1103
+ // apart. No route matched — which this loop, iterating pages it already has,
1104
+ // cannot produce, and is handled anyway so a selected page is never silently
1105
+ // dropped. Or the page's record does not exist (`result.page` is set) — which an
1106
+ // expanded page reaches only if its record is not in the set it was expanded from.
1105
1107
  if (result.outcome === 'notFound') {
1106
- console.warn(` Warning: ${outputRoute} resolved to no page; skipped`)
1108
+ console.warn(
1109
+ ` Warning: ${outputRoute} ${result.page ? 'names a record that does not exist' : 'resolved to no page'}; skipped`
1110
+ )
1107
1111
  continue
1108
1112
  }
1109
1113