@real-router/react 0.27.2 → 0.27.4

package/src/ssr.ts

@@ -1,43 +0,0 @@
-// SSR-feature entry — React 19.2+
-//
-// Server-side and SSR-aware client components/hooks. Importing from this
-// subpath instead of the main entry signals "this code path is part of
-// the SSR pipeline" and makes server-only types stay out of the client
-// TypeScript context for app code that doesn't touch SSR.
-//
-// Trigger for the split: ≥3 SSR-feature exports (#604 + #610 = 5 exports).
-// See `.claude/SSR_FEATURE_GAPS_RU.md` §8 for the architectural rationale.
-
-// Components
-export { ClientOnly } from "./components/ClientOnly";
-
-export { ServerOnly } from "./components/ServerOnly";
-
-export { Await } from "./components/Await";
-
-export { Streamed } from "./components/Streamed";
-
-export { HttpStatusCode } from "./components/HttpStatusCode";
-
-export { HttpStatusProvider } from "./components/HttpStatusProvider";
-
-// Hooks
-export { useDeferred } from "./hooks/useDeferred";
-
-// Utilities
-export { createHttpStatusSink } from "./utils/createHttpStatusSink";
-
-// Types
-export type { ClientOnlyProps } from "./components/ClientOnly";
-
-export type { ServerOnlyProps } from "./components/ServerOnly";
-
-export type { AwaitProps } from "./components/Await";
-
-export type { StreamedProps } from "./components/Streamed";
-
-export type { HttpStatusCodeProps } from "./components/HttpStatusCode";
-
-export type { HttpStatusProviderProps } from "./components/HttpStatusProvider";
-
-export type { HttpStatusSink } from "./utils/createHttpStatusSink";

package/src/types.ts

@@ -1,40 +0,0 @@
-import type {
-  NavigationOptions,
-  Params,
-  Navigator,
-  State,
-} from "@real-router/core";
-import type { HTMLAttributes, MouseEventHandler } from "react";
-
-export interface RouteState<P extends Params = Params> {
-  route: State<P> | undefined;
-  previousRoute?: State | undefined;
-}
-
-export type RouteContext<P extends Params = Params> = {
-  navigator: Navigator;
-} & RouteState<P>;
-
-export interface LinkProps<
-  P extends Params = Params,
-> extends HTMLAttributes<HTMLAnchorElement> {
-  routeName: string;
-  routeParams?: P;
-  routeOptions?: NavigationOptions;
-  activeClassName?: string;
-  activeStrict?: boolean;
-  ignoreQueryParams?: boolean;
-  /**
-   * URL fragment (decoded form, no leading "#") (#532).
-   * - omitted/`undefined` → preserve current fragment on same-route navigation
-   * - `""` → clear fragment
-   * - non-empty → set fragment
-   *
-   * Requires a URL plugin (browser-plugin or navigation-plugin) for full
-   * round-trip; hash-plugin ignores the prop with a one-time dev warning.
-   */
-  hash?: string;
-  target?: string;
-  onClick?: MouseEventHandler<HTMLAnchorElement>;
-  onMouseOver?: MouseEventHandler<HTMLAnchorElement>;
-}

package/src/utils/createHttpStatusSink.ts

@@ -1,27 +0,0 @@
-/**
- * Render-scoped HTTP status sink. Created per request on the server, passed to
- * `<HttpStatusProvider sink={...}>`, and read after `renderToString` /
- * `renderToReadableStream` to apply the value to the HTTP response.
- *
- * Last write wins: if the rendered tree mounts more than one
- * `<HttpStatusCode />`, the value reflects the last component that ran during
- * the render pass.
- *
- * No-op on the client — `<HttpStatusCode />` reads the optional context and
- * skips the write when no provider is mounted, so the same component tree can
- * be hydrated without changing behaviour.
- *
- * Constraints:
- * - **Per-request only.** Don't share a sink across requests; the rendered
- *   tree mutates `code` in place. Module-level singletons leak status
- *   between concurrent requests.
- * - **Don't `Object.freeze` the sink.** The component writes to `.code`;
- *   freezing makes the assignment throw under ESM strict mode.
- */
-export interface HttpStatusSink {
-  code: number | undefined;
-}
-
-export function createHttpStatusSink(): HttpStatusSink {
-  return { code: undefined };
-}