@octanejs/app-core 0.1.7 → 0.1.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@octanejs/app-core",
-  "version": "0.1.7",
+  "version": "0.1.8",
   "license": "MIT",
   "type": "module",
   "engines": {
@@ -79,10 +79,10 @@
     "esbuild": "^0.28.1"
   },
   "peerDependencies": {
-    "octane": "^0.13.2"
+    "octane": "^0.14.0"
   },
   "devDependencies": {
     "@types/node": "^24.13.3",
-    "octane": "0.13.2"
+    "octane": "0.14.0"
   }
 }

package/src/server/component-wrappers.js

@@ -69,10 +69,10 @@ export function createLayoutWrapper(Layout, Page, pageProps) {
 export function createRootBoundaryWrapper(Content, boundary, runtime) {
 	let body = Content;
 
-	// Compose the catch boundary closest to the route. A Suspense boundary is
-	// allowed to retain its pending shell when an unhandled server render error
-	// reaches it, so putting Suspense inside ErrorBoundary would prevent the
-	// configured catch component from observing ordinary route errors.
+	// Compose the catch boundary closest to the route. As in React, the server
+	// never renders it: a server route error reaches the Suspense boundary, which
+	// ships the pending shell for the browser to render the route, where the
+	// catch component observes a repeated error before Suspense would.
 	if (boundary.catch) {
 		const child = body;
 		const Catch = boundary.catch;