@ecopages/ecopages-jsx 0.2.0-rc.6 → 0.2.0-rc.7

package/README.md

@@ -53,6 +53,12 @@ Radiant support is enabled by default. When `radiant: true`, the plugin keeps th
 
 That means server-rendered `RadiantElement` hosts hydrate in place only when both the SSR markers and the explicit client hydrator are present. Without the client hydrator, Radiant intentionally falls back to a fresh client render on first connect.
 
+### Hydration Semantics: RadiantElement vs. RadiantController
+
+- **`RadiantElement` (DOM Preservation)**: Custom elements extending `RadiantElement` support true in-place hydration. When `@ecopages/radiant/client/install-hydrator` executes before elements connect, existing light-DOM SSR nodes are preserved, retaining DOM node identity, form input state, active focus, and media playback.
+- **`RadiantController` (Activation / Template Re-mount)**: Controllers attached via `[data-controller]` activate when `startControllers(document)` is called. Activation executes the controller's `render()` method and mounts its template fresh into the host container, replacing server-rendered child nodes. Reactive properties and signal bindings remain fully interactive, but individual child DOM nodes are reconstructed.
+- **Guidance**: Use `RadiantElement` when in-place preservation of SSR nodes (e.g., focused inputs, media elements, or CSS transitions) is required. Use `RadiantController` for Stimulus-style progressive enhancement on arbitrary markup where child DOM reconstruction is acceptable.
+
 ```ts
 ecopagesJsxPlugin({
 	radiant: true,
@@ -103,4 +109,5 @@ Important:
 - Cross-integration shell stacks should use `EcoEmbed` from `@ecopages/ecopages-jsx/eco-embed` (or the matching integration adapter). Plain opaque objects fail fast at core foreign-subtree queue boundaries; they are not coerced with `String(object)`. Pass already-serialized HTML when `EcoEmbed` is not needed.
 - Components that may render foreign children must declare those children in `config.dependencies.components`.
 - Ecopages validates mixed-renderer ownership from declared dependencies during render preparation. It does not treat rendered HTML alone as the source of truth.
+- Route-level dependency resolvers can supply Components at request time; Ecopages JSX includes those resolved roots when deciding whether a Foreign Subtree needs handoff.
 - Ecopages JSX keeps raw-markup preservation and asset collection inside the JSX renderer.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ecopages/ecopages-jsx",
-  "version": "0.2.0-rc.6",
+  "version": "0.2.0-rc.7",
   "description": "JSX integration plugin for Ecopages",
   "keywords": [
     "ecopages",
@@ -34,13 +34,13 @@
     "directory": "packages/integrations/ecopages-jsx"
   },
   "dependencies": {
-    "@ecopages/mdx": "0.2.0-rc.6",
+    "@ecopages/mdx": "0.2.0-rc.7",
     "@mdx-js/mdx": "^3.1.1",
     "vfile": "^6.0.3"
   },
   "peerDependencies": {
-    "@ecopages/core": "0.2.0-rc.6",
-    "@ecopages/jsx": "^0.3.0-rc.2",
-    "@ecopages/radiant": "^0.3.0-rc.2"
+    "@ecopages/core": "0.2.0-rc.7",
+    "@ecopages/jsx": "^0.3.0-rc.9",
+    "@ecopages/radiant": "^0.3.0-rc.9"
   }
 }

package/src/ecopages-jsx-renderer.js

@@ -146,6 +146,12 @@ export class EcopagesJsxRenderer extends IntegrationRenderer {
                             locals: options.pageLocals,
                         },
                     },
+                    /**
+                     * @remarks Content components supplied by the Page dependency
+                     * resolver (for example the active MDX entry) carry foreign
+                     * ownership the static Page config cannot declare.
+                     */
+                    foreignChildRoots: options.resolvedPageDependencyComponents,
                     layouts: resolveDocumentShellLayouts({
                         layout: options.Layout,
                         layoutEntries: options.layoutEntries,