ErrorBoundary hydration fails in development if there are any elements in head after Links

[nramovs-sr]

Reproduction

Go to https://stackblitz.com/edit/remix-run-remix-8frxmh

In root.tsx there is a <style> element after <Links>.
In routes/_index.tsx there is an ErrorBoundary, and route component throws an error.

On page refresh SSR works correctly, but hydration fails with Error: Hydration failed because the initial UI does not match what was rendered on the server., and tailwind styles are gone. This only happens in development mode.

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @remix-run/dev: * => 2.9.2 
    @remix-run/node: * => 2.9.2 
    @remix-run/react: * => 2.9.2 
    @remix-run/serve: * => 2.9.2 
    vite: ^5.1.0 => 5.3.0

Used Package Manager

npm

Expected Behavior

Error boundary is shown, tailwind styles work, there is no hydration error.

Actual Behavior

Hydration fails, tailwind styles are missing after hydration

My use case for adding additional elements after <Links> is adding additional styles (that need to override the default styles), where stylesheet I add depends on loader data, so I can't use links route module export.

[github-actions]

Thank you for opening this issue, and our apologies we haven't gotten around to it yet!

With the release of React Router v7 we are sun-setting continued development/maintenance on Remix v2. If you have not already upgraded to React Router v7, we recommend you do so. We've tried to make the upgrade process as smooth as possible with our Future Flags. We are now in the process of cleaning up outdated issues and pull requests to improve the overall hygiene of our repositories.

We plan to continue to address 2 types of issues in Remix v2:

• Bugs that pose security concerns
• Bugs that prevent upgrading to React Router v7

If you believe this issue meets one of those criteria, please respond or create a new issue.

For all other issues, ongoing maintenance will be happening in React Router v7, so:

• If this is a bug, please reopen this issue in that repo with a new minimal reproduction against v7
• If this is a feature request, please open a new Proposal Discussion in React Router, and if it gets enough community support it can be considered for implementation

If you have any questions you can always reach out on Discord. Thanks again for providing feedback and helping us make our framework even better!