@reckona/mreact-router 0.0.148 → 0.0.149

package/README.md

@@ -99,7 +99,7 @@ client-only code. Navigation observers are available from
 
 ## Route Module Exports
 
-- `loader(context)` returns data passed to the page component, or may return or throw a `Response` for redirects and custom responses. The context includes `params`, `queryClient`, `request`, and adapter `env` when one is provided.
+- `loader(context)` returns data passed to the page component, or may return or throw a `Response` for redirects and custom responses. The context includes `params`, `queryClient`, `request`, and adapter `env` when one is provided. `notFound()` and its explicit alias `throwNotFound()` both throw the router-recognized 404 control-flow error.
 - `metadata` injects title, OpenGraph, viewport, and related head tags. Use `RouteMetadata` to type the object; `openGraph.image` and `openGraph.images` accept URL scalars or Next-style image objects with a required `url` field.
 - `generateMetadata(context)` may compute route metadata from resolved loader data, params, and the current request. Static `metadata` is still used as the fallback and base object.
 - `generateStaticParams()` returns dynamic route params to prerender and can import modules transformed by configured Vite plugins.
@@ -178,6 +178,25 @@ const instrumentation: RouterInstrumentation = {
 };
 ```
 
+Use `definePage<typeof loader>()` when a route page should infer `props.data` and `props.params` from its sibling loader without repeating the loader data shape in the page props annotation:
+
+```tsx
+import { definePage, type LoaderContext } from "@reckona/mreact-router";
+
+interface UserData {
+  id: string;
+  name: string;
+}
+
+export async function loader(context: LoaderContext<{ id: string }>): Promise<UserData> {
+  return { id: context.params.id, name: "Ada" };
+}
+
+export default definePage<typeof loader>(function UserPage(props) {
+  return <h1>{props.params.id}: {props.data.name}</h1>;
+});
+```
+
 Use `InferLoaderData<typeof loader>` when sibling modules need the exact data shape returned by a route loader:
 
 ```ts

package/dist/build.js

@@ -3551,7 +3551,7 @@ export { defer, isDeferredLoaderData } from ${JSON.stringify(routerDeferredPath)
 export { defineMessages, detectLocale } from ${JSON.stringify(routerI18nPath)};
 export { Link, linkProps } from ${JSON.stringify(routerLinkPath)};
 export { parseMultipartStream } from ${JSON.stringify(routerMultipartPath)};
-export { cookies, headers, html, json, next, notFound, redirect, redirectExternal, rewrite } from ${JSON.stringify(routerNavigationPath)};
+export { cookies, headers, html, json, next, notFound, redirect, redirectExternal, rewrite, throwNotFound } from ${JSON.stringify(routerNavigationPath)};
 export { getServerRuntimeState } from ${JSON.stringify(routerRuntimeStatePath)};`,
                 loader: "js",
                 resolveDir: dirname(routerNavigationPath),