wtclaude
28f4b9afe2
The 35 files behind twelve public pages, seven admin views, two player views and three core-page extensions, ported onto `window.__rg`. Every one of them imports exactly the seven kit members plus `lib/format.js`, which is the finding §2.7.1 predicted and this confirms. `client/src/core.js` is the port mechanism, and unlike the server's it is a plain read: `window.__rg` is published before any module chunk evaluates, so there is no gap to defer around and a ported component keeps its ordinary import shape. `client/src/api.js` rebuilds the UO namespaces over the request primitive — same URLs, because §1.2 freezes the API surface. SPA paths changed and API paths did not. `/site/shard` is `/uo/shard`, and the admin paths lost their now-redundant `shard-` prefixes (`/admin/uo/ops`), a clean break being the only moment that is free. `shim/rg.js` becomes the single reader of the global, so the "core did not publish its dependencies" message is reachable from whichever module the bundler happens to touch first rather than from whichever one is imported first — a guarantee that used to last until someone sorted the imports. Co-Authored-By: Claude <noreply@anthropic.com>
15 lines
477 B
JavaScript
15 lines
477 B
JavaScript
// `react-dom/client`, from core.
|
|
//
|
|
// A module never calls `createRoot` — core owns the root and the module renders
|
|
// inside it. This exists because a transitive import can still reach for
|
|
// react-dom, and one that resolved to a bundled copy would put a second
|
|
// renderer in the page.
|
|
|
|
import { rg } from './rg.js'
|
|
|
|
const reactDom = rg().reactDom
|
|
|
|
export default reactDom.default ?? reactDom
|
|
|
|
export const { createRoot, hydrateRoot, flushSync, createPortal } = reactDom
|