v0.11.2
Makes the blank-screen class of bug visible, and publishes what the backends need to check themselves against.
resolveEscalatedPage()
Inertia resolves a page name to a component, and a name with nothing behind it is not an error — resolve() returns undefined, Vue renders nothing, and the panel comes up blank on a 200 response. It reads as a permissions problem or an empty dataset. Four screens shipped that way.
createInertiaApp({
resolve: (name) =>
resolveEscalatedPage(name, () =>
resolvePageComponent(`./Pages/${name}.vue`, import.meta.glob('./Pages/**')),
),
});Throws in development, naming what was asked for and the nearest thing that exists; logs and renders the same message in production. Suggestions rank on path-segment overlap rather than leaf equality — nearly every page ends in Index or Form.
pages.json
Every page name this package can resolve, generated from src/pages and exported at @escalated-dev/escalated/pages.json. It is what each backend checks its own names against in CI — the only place both halves of that comparison are known.
npm run pages:check fails if it has drifted from the components, and lint runs it.
637 tests.