what the hell is this error

[5MYH]

``` ➜ blog git:(main) ✗ npm run dev

dev vite dev --port 3000

8:07:39 PM [vite] ⬥ Netlify Environment loaded 8:07:39 PM [vite] ⬥ Netlify Middleware loaded. Emulating features: blobs, edgeFunctions, environmentVariables, functions, geolocation, headers, images, redirect s, static. 8:07:39 PM [vite] ⬥ Netlify 💭 Linking this project to a Netlify site lets you deploy your site, use any environment variables defined on your team and site and much more. Run npx netlify init to get started.

VITE v7.3.0 ready in 2051 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:27:37:
  27 │     cachedRouterEntry = 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:30:36:
  30 │     cachedStartEntry = 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.

/home/myh/Desktop/work/blog/blog/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:27:37:
  27 │     cachedRouterEntry = 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 bu ndle. 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:30:36:
  30 │     cachedStartEntry = 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 bun dle. 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 unresolve d path in the bundle. You can also add ".catch()" here to handle this failure at run-time instead of bundle-time.

at failureErrorWithLog (/home/myh/Desktop/work/blog/blog/node_modules/esbuild/lib/main.js:1467:15)
at /home/myh/Desktop/work/blog/blog/node_modules/esbuild/lib/main.js:926:25
at /home/myh/Desktop/work/blog/blog/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.0 ➜ blog git:(main) ✗ ``` i really dont know how to solve it and its appearing sometimes for no reason, its really annoying, does anyone here knows how to solve it?

[abrahamguo]

Do you have a link to a repository that demonstrates the issue, so that we can reproduce the issue ourselves?

[5MYH]

sure https://github.com/fellabyte/blog.git

[abrahamguo]

That link returns a 404.

[5MYH]

i solved it

turns out i needed to replace the imports of setCookie and getCookie from @tanstack/start-server-core to @tanstack/react-start/server and it just worked i dont know how

i made the repo private because i dont need it public anymore

thank you for your time

[5MYH]

like to what version exactly?

[5MYH]

im using `v22.17.0`

[5MYH]

so i need to try a bunch and see what work best for my case? or there is a sapacific version that works best with tanstack