Skip to content

Conversation

@github-actions
Copy link
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to release-next, this PR will be updated.

Releases

[email protected]

Patch Changes

  • [UNSTABLE] Add location/params as arguments to client-side unstable_onError to permit enhanced error reporting. (#14509)

    ⚠️ This is a breaking change if you've already adopted unstable_onError. The second errorInfo parameter is now an object with location and params:

    // Before
    function errorHandler(error: unknown, errorInfo?: React.errorInfo) {
      /*...*/
    }
    
    // After
    function errorHandler(
      error: unknown,
      info: {
        location: Location;
        params: Params;
        errorInfo?: React.ErrorInfo;
      },
    ) {
      /*...*/
    }
  • Properly handle ancestor thrown middleware errors before next() on fetcher submissions (#14517)

  • Fix issue with splat routes interfering with multiple calls to patchRoutesOnNavigation (#14487)

  • Normalize double-slashes in resolvePath (#14529)

@react-router/[email protected]

Patch Changes

@react-router/[email protected]

Patch Changes

@react-router/[email protected]

Patch Changes

  • Use a dynamic import() to load ESM-only p-map dependency to avoid issues on Node 20.18 and below (#14492)
  • Short circuit HEAD document requests before calling renderToPipeableStream in the default entry.server.tsx to more closely align with the spec (#14488)
  • Updated dependencies:

[email protected]

Patch Changes

@react-router/[email protected]

Patch Changes

@react-router/[email protected]

Patch Changes

@react-router/[email protected]

Patch Changes

@react-router/[email protected]

Patch Changes

@react-router/[email protected]

Patch Changes

[email protected]

@github-actions github-actions bot force-pushed the changeset-release/release-next branch from 852357a to 9293a48 Compare November 13, 2025 17:18
@brophdawg11 brophdawg11 merged commit e75da95 into release-next Nov 13, 2025
1 check passed
@brophdawg11 brophdawg11 deleted the changeset-release/release-next branch November 13, 2025 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants