Could not resolve "#tanstack-router-entry" #5795

Activity

1. schiller-manuel commented on Nov 8, 2025

   

   schiller-manuel

   on Nov 8, 2025

   Collaborator

   More actions

   please share a full reproduction project
2. schiller-manuel

   added

   information neededFurther information is requestedFurther information is requested

   on Nov 8, 2025
3. guillemus commented on Nov 10, 2025

   

   guillemus

   on Nov 10, 2025

   More actions

   not op but I have the same error in this repo

   https://github.com/guillemus/tanstack-mpa

   This happened after I tried to add better auth. Maybe it is bc there's no entry-client / server files? That's what haiku suggested me but idk.

   here's the full output:

   
   ➜  tanstack-mpa git:(main) ✗ bun dev
   $ vite dev --port 3000
   
     VITE v7.2.2  ready in 417 ms
   
     ➜  Local:   http://localhost:3000/
     ➜  Network: use --host to expose
     ➜  press h + enter to show help
   ✘ [ERROR] Could not resolve "#tanstack-router-entry"
   
       node_modules/@tanstack/start-server-core/dist/esm/createStartHandler.js:29:33:
         29 │       routerEntry = await import("#tanstack-router-entry");
            ╵                                  ~~~~~~~~~~~~~~~~~~~~~~~~
   
     The package import "#tanstack-router-entry" is not defined in this "imports" map:
   
       node_modules/@tanstack/start-server-core/package.json:49:13:
         49 │   "imports": {
            ╵              ^
   
     You can mark the path "#tanstack-router-entry" as external to exclude it from the bundle, which
     will remove this error and leave the unresolved path in the bundle. You can also add ".catch()"
     here to handle this failure at run-time instead of bundle-time.
   
   ✘ [ERROR] Could not resolve "#tanstack-start-entry"
   
       node_modules/@tanstack/start-server-core/dist/esm/createStartHandler.js:32:32:
         32 │       startEntry = await import("#tanstack-start-entry");
            ╵                                 ~~~~~~~~~~~~~~~~~~~~~~~
   
     The package import "#tanstack-start-entry" is not defined in this "imports" map:
   
       node_modules/@tanstack/start-server-core/package.json:49:13:
         49 │   "imports": {
            ╵              ^
   
     You can mark the path "#tanstack-start-entry" as external to exclude it from the bundle, which
     will remove this error and leave the unresolved path in the bundle. You can also add ".catch()"
     here to handle this failure at run-time instead of bundle-time.
   
   ✘ [ERROR] Could not resolve "tanstack-start-manifest:v"
   
       node_modules/@tanstack/start-server-core/dist/esm/router-manifest.js:3:44:
         3 │   const { tsrStartManifest } = await import("tanstack-start-manifest:v");
           ╵                                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
     You can mark the path "tanstack-start-manifest:v" as external to exclude it from the bundle, which
     will remove this error and leave the unresolved path in the bundle. You can also add ".catch()"
     here to handle this failure at run-time instead of bundle-time.
   
   ✘ [ERROR] Could not resolve "tanstack-start-injected-head-scripts:v"
   
       node_modules/@tanstack/start-server-core/dist/esm/router-manifest.js:9:49:
         9 │     const { injectedHeadScripts } = await import("tanstack-start-injected-head-scripts:v");
           ╵                                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
     You can mark the path "tanstack-start-injected-head-scripts:v" as external to exclude it from the
     bundle, which will remove this error and leave the unresolved path in the bundle. You can also add
     ".catch()" here to handle this failure at run-time instead of bundle-time.
   
   /Users/guillem/Documents/projects/tanstack-mpa/node_modules/esbuild/lib/main.js:1467
     let error = new Error(text);
                 ^
   
   Error: Error during dependency optimization:
   
   ✘ [ERROR] Could not resolve "#tanstack-router-entry"
   
       node_modules/@tanstack/start-server-core/dist/esm/createStartHandler.js:29:33:
         29 │       routerEntry = await import("#tanstack-router-entry");
            ╵                                  ~~~~~~~~~~~~~~~~~~~~~~~~
   
     The package import "#tanstack-router-entry" is not defined in this "imports" map:
   
       node_modules/@tanstack/start-server-core/package.json:49:13:
         49 │   "imports": {
            ╵              ^
   
     You can mark the path "#tanstack-router-entry" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add ".catch()" here to handle this failure at run-time instead of bundle-time.
   
   
   ✘ [ERROR] Could not resolve "#tanstack-start-entry"
   
       node_modules/@tanstack/start-server-core/dist/esm/createStartHandler.js:32:32:
         32 │       startEntry = await import("#tanstack-start-entry");
            ╵                                 ~~~~~~~~~~~~~~~~~~~~~~~
   
     The package import "#tanstack-start-entry" is not defined in this "imports" map:
   
       node_modules/@tanstack/start-server-core/package.json:49:13:
         49 │   "imports": {
            ╵              ^
   
     You can mark the path "#tanstack-start-entry" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add ".catch()" here to handle this failure at run-time instead of bundle-time.
   
   
   ✘ [ERROR] Could not resolve "tanstack-start-manifest:v"
   
       node_modules/@tanstack/start-server-core/dist/esm/router-manifest.js:3:44:
         3 │ ...t { tsrStartManifest } = await import("tanstack-start-manifest:v");
           ╵                                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
     You can mark the path "tanstack-start-manifest:v" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add ".catch()" here to handle this failure at run-time instead of bundle-time.
   
   
   ✘ [ERROR] Could not resolve "tanstack-start-injected-head-scripts:v"
   
       node_modules/@tanstack/start-server-core/dist/esm/router-manifest.js:9:49:
         9 │ ...Scripts } = await import("tanstack-start-injected-head-scripts:v");
           ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   
     You can mark the path "tanstack-start-injected-head-scripts:v" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add ".catch()" here to handle this failure at run-time instead of bundle-time.
   
   
       at failureErrorWithLog (/Users/guillem/Documents/projects/tanstack-mpa/node_modules/esbuild/lib/main.js:1467:15)
       at /Users/guillem/Documents/projects/tanstack-mpa/node_modules/esbuild/lib/main.js:926:25
       at /Users/guillem/Documents/projects/tanstack-mpa/node_modules/esbuild/lib/main.js:1345:9
       at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
     errors: [Getter/Setter],
     warnings: [Getter/Setter]
   }
   
   Node.js v22.17.1
   error: script "dev" exited with code 1
   
   
4. guillemus commented on Nov 10, 2025

   

   guillemus

   on Nov 10, 2025

   More actions

   @schiller-manuel I found what causes the issue somehow.

   to reproduce:

   • clone the repo
   • rm -rf .tanstack && bun i
   • you should see the error when running bun dev
   • comment out all code from counter.ts file
   • bun dev should now work.
   • uncomment back the code from counter.ts
   • bun dev should now work with the original code.

   I hope this helps
5. austinm911 commented on Nov 10, 2025

   

   austinm911

   on Nov 10, 2025

   Author

   More actions

   @guillemus Even adding the client/server.ts entry files, I run into the same issues as well
6. theoludwig commented on Nov 11, 2025

   

   theoludwig

   on Nov 11, 2025

   More actions

   I have the same issue but with Vitest.

   👍React with 👍2Reacted by Simon and Anton Moiseev
7. schiller-manuel commented on Nov 11, 2025

   

   schiller-manuel

   on Nov 11, 2025

   Collaborator

   More actions

   @theoludwig can you share a reproducer project with vitest?

   👀React with 👀1Reacted by Austin
8. theoludwig commented on Nov 11, 2025

   

   theoludwig

   on Nov 11, 2025

   Last edited by theoludwig

   More actions

   @theoludwig can you share a reproducer project with vitest?

   Sure, here it is: https://github.com/theoludwig/vite-nitro-issues/tree/vitest-issue

   To reproduce:

   1. git clone git@github.com:theoludwig/vite-nitro-issues.git
   2. cd vite-nitro-issues
   3. git checkout vitest-issue
   4. pnpm install --frozen-lockfile
   5. node --run test
9. gianlazaro commented on Nov 20, 2025

   

   gianlazaro

   on Nov 20, 2025

   More actions

   I'll see if I have time to make a reproducer sometime this week, but I'm having this exact issue when I install a specific library.

   better-auth@beta (since 1.4 stable is coming out Friday)

   👍React with 👍1Reacted by Dalibor Homola
10. rollsrobby commented on Nov 20, 2025

    

    rollsrobby

    on Nov 20, 2025

    More actions

    I only see this issue if I enable the reactStartCookie plugin by better-auth.
    And only after removing the node_modules folder and reinstalling(pnpm install).
    If I remove the plugin, clean, install. All works fine.
    Maybe this observation helps..

    🎉React with 🎉7Reacted by Gian, sam, Nehuen, Dalibor Homola, Fabrizzio Lo Presti, Ben Griffith and dmtnndxr
11. gianlazaro commented on Nov 20, 2025

    

    gianlazaro

    on Nov 20, 2025

    Last edited by gianlazaro

    More actions

    @rollsrobby That did the trick for me!

    It got me curious and looked into what could possibly be making this issue.

    I was able to reproduce the original poster's issue by using setCookie imported from "@tanstack/react-start/server" (used in certain cases). I hope this narrows it down for you, @schiller-manuel

    update: I guess it's mostly affects improper uses of functions that should only run on the server like setting cookies, or headers that causes the error.
12. 2bdelghafour commented on Nov 20, 2025

    

    2bdelghafour

    on Nov 20, 2025

    More actions

    @gianlazaro I ran into the same issue when using Better Auth with Tanstack Start and I can see there is already a PR open on their end to fix it by using the proper imports

    better-auth/better-auth#6045

    🚀React with 🚀1Reacted by Gian
13. dotnize commented on Nov 22, 2025

    

    dotnize

    on Nov 22, 2025

    Last edited by dotnize

    Contributor

    More actions

    For better-auth users this has been fixed in ^1.4.1

    • chore: remove unused @tanstack/start-server-core and move to @tanstack/react-start better-auth/better-auth#6209

    👍React with 👍1Reacted by Dalibor Homola
14. gianlazaro commented on Nov 26, 2025

    

    gianlazaro

    on Nov 26, 2025

    Last edited by gianlazaro

    More actions

    @dotnize @2bdelghafour

    1.4.1 fixed the issue but 1.4.2 (released a couple of hours ago) reverts back to importing start-server-core because it apparently fixes the cookies issue on with solid on tanstack start.

    We're back to the same issue.

    better-auth/better-auth#6235

    👍React with 👍4Reacted by Nathaniel John Tampus, Andrés B.R, Guillem Garcia and Bryan

    😄React with 😄1Reacted by Dalibor Homola
15. dotnize

    added a commit that references this issue on Nov 26, 2025

    fix: temporarily lock to better-auth 1.4.1 (TanStack/router#5795 (com…

    ...

    9211560
16. 22 remaining items

    Load more
17. dotnize

    added a commit that references this issue on Jan 16, 2026

    temp: downgrade better-auth to 1.4.12 (TanStack/router#5795 (comment))

    7912c30
18. web-dev-sayantan commented on Jan 16, 2026

    

    web-dev-sayantan

    on Jan 16, 2026

    More actions

    Facing the same issue with @tanstack/* 1.150.0 and better-auth 1.4.13 in my repo,
    Opus 4.5 went on a crazy run, and fixed it for now with bunch of weird config in vite.config.ts, half of which I don't understand.

    import { defineConfig } from 'vite'
    import { tanstackStart } from '@tanstack/react-start/plugin/vite'
    import viteReact from '@vitejs/plugin-react'
    import viteTsConfigPaths from 'vite-tsconfig-paths'
    import tailwindcss from '@tailwindcss/vite'
    import { cloudflare } from '@cloudflare/vite-plugin'
    import type { Plugin as EsbuildPlugin } from 'esbuild'
    
    // Plugin to mark TanStack Start virtual modules as external
    const tanstackExternalPlugin: EsbuildPlugin = {
      name: 'tanstack-external',
      setup(build) {
        build.onResolve({ filter: /^#tanstack-|^tanstack-start-/ }, () => ({
          external: true,
        }))
      },
    }
    
    export default defineConfig({
      server: {
        port: 3000,
      },
      plugins: [
        tailwindcss(),
        viteTsConfigPaths({
          projects: ['./tsconfig.json'],
        }),
        cloudflare({
          viteEnvironment: { name: 'ssr' },
          inspectorPort: false,
        }),
        tanstackStart(),
        viteReact(),
      ],
      optimizeDeps: {
        esbuildOptions: {
          plugins: [tanstackExternalPlugin],
        },
      },
      environments: {
        ssr: {
          optimizeDeps: {
            esbuildOptions: {
              plugins: [tanstackExternalPlugin],
            },
          },
        },
      },
      build: {
        rollupOptions: {
          external: ['cloudflare:workers'],
        },
      },
    })

    👍React with 👍1Reacted by Ludovico Russo
19. ludusrusso commented on Jan 16, 2026

    

    ludusrusso

    on Jan 16, 2026

    More actions

    @tanstack/* 1.150.0 and better-auth 1.4.13 in my repo

    same here
20. joshymcd commented on Jan 16, 2026

    

    joshymcd

    on Jan 16, 2026

    More actions

    I was just having this issue.
    For me excluding my Tanstack packages from Vites dev server optimisations seemed to do the trick

    vite.config.ts

      optimizeDeps: {
        // Exclude TanStack Start packages from Vite's dependency optimization
        // to prevent issues with virtual imports (#tanstack-router-entry, etc.)
        exclude: [
          '@tanstack/start-server-core',
          '@tanstack/react-start',
          '@tanstack/react-start/client',
          '@tanstack/react-start/server',
        ],
      },

    👍React with 👍5Reacted by Jhonatan Macazana, Vincent Parrett, CodeAlias, Ibrahim Mohammed and Yaroslav Lisovets

    ❤️React with ❤️7Reacted by Jhonatan Macazana, Tung Tran, Sornchai Somsakul, Kusal Kalinga, Angelo Calabrò, Ilyas Adiyasa and Yaroslav Lisovets
21. williiam-tran commented on Jan 17, 2026

    

    williiam-tran

    on Jan 17, 2026

    More actions

    I was just having this issue. For me excluding my Tanstack packages from Vites dev server optimisations seemed to do the trick

    vite.config.ts

    optimizeDeps: {
    // Exclude TanStack Start packages from Vite's dependency optimization
    // to prevent issues with virtual imports (#tanstack-router-entry, etc.)
    exclude: [
    '@tanstack/start-server-core',
    '@tanstack/react-start',
    '@tanstack/react-start/client',
    '@tanstack/react-start/server',
    ],
    },

    This works for me!
22. kusalkalinga00 commented on Jan 17, 2026

    

    kusalkalinga00

    on Jan 17, 2026

    More actions

    I was just having this issue. For me excluding my Tanstack packages from Vites dev server optimisations seemed to do the trick

    vite.config.ts

    optimizeDeps: {
    // Exclude TanStack Start packages from Vite's dependency optimization
    // to prevent issues with virtual imports (#tanstack-router-entry, etc.)
    exclude: [
    '@tanstack/start-server-core',
    '@tanstack/react-start',
    '@tanstack/react-start/client',
    '@tanstack/react-start/server',
    ],
    },

    This worked for me also. Issue started to originate when I migrate from bun to pnpm.
23. rgripper commented on Jan 17, 2026

    

    rgripper

    on Jan 17, 2026

    More actions

    I was just having this issue. For me excluding my Tanstack packages from Vites dev server optimisations seemed to do the trick

    vite.config.ts

    optimizeDeps: {
    // Exclude TanStack Start packages from Vite's dependency optimization
    // to prevent issues with virtual imports (#tanstack-router-entry, etc.)
    exclude: [
    '@tanstack/start-server-core',
    '@tanstack/react-start',
    '@tanstack/react-start/client',
    '@tanstack/react-start/server',
    ],
    },

    didnt help, I still have the same error

    👍React with 👍1Reacted by Bryson Meiling
24. astralarya commented on Jan 17, 2026

    

    astralarya

    on Jan 17, 2026

    More actions

    I started getting similar errors upgrading from 1.149.1 -> 1.151.1, which I was able to resolve by adding this to my vite config:

      optimizeDeps: {
        exclude: [
          "@tanstack/start-server-core",
          "@tanstack/start-client-core",
          "@tanstack/react-start",
        ],
      },

    On one hand, I'm glad that this fixes it, but on the other hand, I wish it weren't necessary.
25. bytaesu commented on Jan 18, 2026

    

    bytaesu

    on Jan 18, 2026

    More actions

    from Better Auth,
    We've worked on this, I tested it in the actual app, and I can confirm that it's fixed now in v1.4.15 😄

    • fix: update TanStack imports to use server subpath better-auth/better-auth#7446

    👍React with 👍6Reacted by Nathaniel John Tampus, Vladimir Zotov, Amruth Pillai, Herc, Waishnav and Austin

    🎉React with 🎉5Reacted by Nathaniel John Tampus, Amruth Pillai, Herc, Sayantan Dey and Austin

    ❤️React with ❤️4Reacted by Nathaniel John Tampus, Vladimir Zotov, Amruth Pillai and Herc
26. MarcusGasberg commented on Jan 24, 2026

    

    MarcusGasberg

    on Jan 24, 2026

    More actions

    Weirdly enough I still encountered it after upgrading, when I tried to deploy to Cloudflare workers. The issue was due to having multiple environments in my wrangler.toml and not passing the correct CLOUDFLARE_ENV to my build command. I also had to point to the generated wrangler.json file.

    Previous build command:

        "deploy:staging": "bun run build && bunx wrangler deploy --env=\"staging\" --keep-vars --config ./wrangler.toml",\
    

    Fixed:

       "deploy:staging": "CLOUDFLARE_ENV=staging bun run build && bunx wrangler deploy --keep-vars --config ./dist/server/wrangler.json",
    
27. isc30 commented on Feb 16, 2026

    

    isc30

    on Feb 16, 2026

    More actions

    I started getting similar errors upgrading from 1.149.1 -> 1.151.1, which I was able to resolve by adding this to my vite config:

    optimizeDeps: {
    exclude: [
    "@tanstack/start-server-core",
    "@tanstack/start-client-core",
    "@tanstack/react-start",
    ],
    },
    On one hand, I'm glad that this fixes it, but on the other hand, I wish it weren't necessary.

    is this the properly-done-accepted way or just a hack?
28. isc30 commented on Feb 19, 2026

    

    isc30

    on Feb 19, 2026

    More actions

    For the proper solution, see better-auth/better-auth#6045 (comment)
    Basically, replace the imports from @tanstack/react-start-server to @tanstack/react-start/server and vite will be happy.

    I believe this would be a good addition to the eslint plugin, to inform users to use the proper import to avoid vite dependency optimization issues.
29. barbalex commented on Feb 27, 2026

    

    barbalex

    on Feb 27, 2026

    Last edited by barbalex

    More actions

    Not sure if this is the same issue: In an app using tanstack router I tried to use tanstack start (to add server routes). When replacing TanStackRouterVite({ target: 'react', autoCodeSplitting: true }) with tanstackStart() I immediately get this error:

    TypeError: entries.routerEntry.getRouter is not a function
        at getRouter (/home/alex/Documents/GitHub/ps/node_modules/@tanstack/start-server-core/src/createStartHandler.ts:472:44)
        ... 8 lines matching cause stack trace ...
        at async Object.fetch (/home/alex/Documents/GitHub/ps/node_modules/@tanstack/react-start/dist/plugin/default-entry/server.ts:16:14) {
      cause: TypeError: entries.routerEntry.getRouter is not a function
          at getRouter (/home/alex/Documents/GitHub/ps/node_modules/@tanstack/start-server-core/src/createStartHandler.ts:472:44)
          at handleServerRoutes (/home/alex/Documents/GitHub/ps/node_modules/@tanstack/start-server-core/src/createStartHandler.ts:724:24)
          at eval (/home/alex/Documents/GitHub/ps/node_modules/@tanstack/start-server-core/src/createStartHandler.ts:606:28)
          at AsyncLocalStorage.run (node:internal/async_local_storage/async_context_frame:63:14)
          at runWithStartContext (/home/alex/Documents/GitHub/ps/node_modules/@tanstack/start-storage-context/src/async-local-storage.ts:34:23)
          at requestHandlerMiddleware (/home/alex/Documents/GitHub/ps/node_modules/@tanstack/start-server-core/src/createStartHandler.ts:596:16)
          at next (/home/alex/Documents/GitHub/ps/node_modules/@tanstack/start-server-core/src/createStartHandler.ts:279:22)
          at executeMiddleware (/home/alex/Documents/GitHub/ps/node_modules/@tanstack/start-server-core/src/createStartHandler.ts:301:10)
          at startRequestResolver (/home/alex/Documents/GitHub/ps/node_modules/@tanstack/start-server-core/src/createStartHandler.ts:627:25)
          at async Object.fetch (/home/alex/Documents/GitHub/ps/node_modules/@tanstack/react-start/dist/plugin/default-entry/server.ts:16:14),
      status: 500,
      statusText: undefined,
      headers: undefined,
      data: undefined,
      body: undefined,
      unhandled: true
    }

    👍React with 👍1Reacted by GabenGar
30. johnjensenish

    added a commit that references this issue on May 3, 2026

    Bump dependencies (#35)

    ...

    37c4ff3
31. escwxyz commented on May 4, 2026

    

    escwxyz

    on May 4, 2026

    More actions

    Same error for basic start example with RSC, no better-auth, vite 8.

    Repro: https://github.com/escwxyz/tanstack-rsc-test

    

    👀React with 👀2Reacted by Vladimir Zotov and Demian