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>
30 lines
1.4 KiB
JavaScript
30 lines
1.4 KiB
JavaScript
// The one place this module reads `window.__rg`, and the one place that says
|
|
// something useful when it is not there.
|
|
//
|
|
// Every shim beside this file, and `src/core.js`, go through here. That is not
|
|
// tidiness — it removes an ordering dependency that was genuinely fragile. ES
|
|
// modules evaluate dependencies in the source order of their import statements,
|
|
// so "put the friendly check in the file that is imported first" is a guarantee
|
|
// that survives exactly until someone sorts the imports. Whichever module the
|
|
// bundler happens to reach first, it reaches `window.__rg` through this.
|
|
//
|
|
// A missing global means core did not publish its shared dependencies before
|
|
// this chunk evaluated: an injection or ordering fault in CORE (MODULE_API.md
|
|
// §3.1), not a fault in this module. Without this, the first symptom is
|
|
// "Cannot read properties of undefined (reading 'react')" thrown from a file
|
|
// called react.js, which reads like the module bundled React wrong — the
|
|
// opposite of what happened.
|
|
export function rg() {
|
|
const shared = window.__rg
|
|
if (!shared) {
|
|
throw new Error(
|
|
'[module-uo] window.__rg is missing — core did not publish its shared dependencies before this ' +
|
|
'chunk evaluated. That is an injection or ordering fault in core (MODULE_API.md §3.1), not a ' +
|
|
'fault in this module.',
|
|
)
|
|
}
|
|
return shared
|
|
}
|
|
|
|
export default rg
|