Skip to content
Source
Sign inSign up
TanStack/router

[SOLID] tanstack start 1.136.11 (looks like 1.136.9?) causes hydration errors #5898

Send to my agent
Closedelite174(GitHub profile, opens in a new tab) opened this issue 6 comments

Which project does this relate to?

Start

Describe the bug

I had 1.136.8, updated to 1.136.11, didn't change my code, and now I always get hydration mismatch errors.

Your Example Website or App

Steps to Reproduce the Bug or Issue

Expected behavior

Should work without errors

Screenshots or Videos

No response

Platform

  • start 1.136.11
  • vite 7.2.2

Additional context

No response

  1. Even if I remove Outlet from the root and leave it like:

    export const Route = createRootRouteWithContext<AppContext>()({
      head: () => ({
        meta: [
          { charSet: "utf-8" },
          { name: "viewport", content: "width=device-width, initial-scale=1" },
        ],
      }),
      component: () => (
        <html>
          <head>
            <HydrationScript />
            <HeadContent />
            <link rel="icon" type="image/png" sizes="32x32" href={appIcon} />
            <link rel="apple-touch-icon" sizes="180x180" href={appTouchIcon} />
          </head>
          <body>
            <noscript>You need to enable JavaScript to run this app.</noscript>
            <div id="root" style="isolation: isolate">
            </div>
            <div id="loading-line-root" style="isolation: isolate"></div>
            <div id="upload-list-popup-root" style="isolation: isolate"></div>
            <div id="notifications-root" style="isolation: isolate"></div>
            <Scripts />
          </body>
        </html>
      ),
      notFoundComponent: () => {
        const navigate = useNavigate();
    
        navigate({ to: "/videos" });
    
        return null;
      },
    });

    Still get hydration mismatch

  2. Looks like the issue occurred in 1.136.9 version

  3. The error is in Asset.tsx file

    Image
  4. birkskyum(GitHub profile, opens in a new tab) added labelspackage: solid-start

  5. @elite174 there should be a 1.136.12 release out any minute now, that I believe resolves this issue. Let me know if it's working as expected.

  6. Wow, thank you! Will check soon

Sign in to join this conversation.