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>
51 lines
1.4 KiB
JavaScript
51 lines
1.4 KiB
JavaScript
// The shared React, taken from core rather than bundled.
|
|
//
|
|
// Why a shim file exists at all (MODULE_API.md §3.6, and the spike proved it the
|
|
// hard way): Rollup's `external` alone emits a bare `import 'react'` into the
|
|
// chunk, which the browser cannot resolve without an import map — and an import
|
|
// map has to be an inline `<script type="importmap">`, which core's
|
|
// `script-src 'self'` forbids. `output.globals` does not help either; it is
|
|
// iife/umd only, and this is an ES module. So each shared dependency is aliased
|
|
// to a two-line module that re-exports from the global core published before any
|
|
// module chunk evaluated.
|
|
//
|
|
// The named re-exports are not decoration: `import { useState } from 'react'`
|
|
// compiles to a named import, and a module with only a default export would fail
|
|
// at link time in the browser with a message about the binding, not about this.
|
|
|
|
import { rg } from './rg.js'
|
|
|
|
const react = rg().react
|
|
|
|
export default react.default ?? react
|
|
|
|
export const {
|
|
Children,
|
|
Component,
|
|
Fragment,
|
|
StrictMode,
|
|
Suspense,
|
|
cloneElement,
|
|
createContext,
|
|
createElement,
|
|
forwardRef,
|
|
isValidElement,
|
|
lazy,
|
|
memo,
|
|
useCallback,
|
|
useContext,
|
|
useDebugValue,
|
|
useDeferredValue,
|
|
useEffect,
|
|
useId,
|
|
useImperativeHandle,
|
|
useInsertionEffect,
|
|
useLayoutEffect,
|
|
useMemo,
|
|
useReducer,
|
|
useRef,
|
|
useState,
|
|
useSyncExternalStore,
|
|
useTransition,
|
|
} = react
|