remix

Reproduction Package: · Version:** 0.8.0, and current (checked today) removes `renderToStringclientEntryrenderToStringclientEntry/bGET /b200renderToStringrenderToStreamrenderToStringrenderToStringrenderToStreampackages/ui/src/server/stream.ts#L1480-L1490runtime/navigation.tsdata-rmx-documentdownloadruntime/frame.tsconsumeFlushBatches()applied: falseoptions.flushKind === 'document'flushKindpackages/ui/src/server/README.mdrenderToStringrenderToStringrenderToStringrenderToStreamrenderDocumentToStringonErrorrenderToStringremix new` app. Say the word and I will put up a minimal repository. Expected Behavior Clicking an internal on a page that carries a clientEntry navigates: the document is swapped for the destination that was just fetched. Actual Behavior The URL changes and the document does not. The destination is fetched and returns 200. No thrown error, no onError call, nothing in the console — the response is dropped because it carries no marker.

Reproduction https://github.com/joejemmely/remix-template-redirect-repro Using Remix 3.0.0-rc.1. This minimal app preserves the template's browser entry and replaces the starter UI with a POST form whose action returns a redirect to another page. No database or persistence is needed. 1. Clone the reproduction and run (Node >=24.3.0). 2. Run . 3. Open http://localhost:44100/edit with JavaScript enabled and wait for the runtime to load. 4. Click Save. Confirmed in Chromium. passes, and confirms the server returns HTTP 303 with . Expected Behavior The Saved page renders and the browser URL changes from to . Actual Behavior The Saved page renders, but the browser URL remains . The template's custom returns or , discarding the redirect metadata the runtime needs. The current upstream template entry still contains this resolver. Removing the custom resolver and its helper fixes this by using Remix's default resolver. Confirmed with the same reproduction: the Saved page renders and the URL becomes . Related: #11667 introduced redirect handling for results; #11693 added the default resolver and updated demos, but the root template still contains the custom resolver.

This adds Standard JSON Schema support for the remix/data-schema package. I tried to keep changes to current code minimal, only adding the property to the schemas, and a method to set a title, description and custom jsonSchema (used for case like ), all optional. The API is simple, once you define a schema: You can now call and get an the JSON schema object You can then pass this object to any package that expects a JSON schema. If the data-schema has something that can't be converted (like a Set, Map, etc.) then it immediately throw so ideally you catch this at dev time. I also avoided intentionally to change or adjust any existing test, so everything that already works still works, this is purely additive changes.