Could not resolve "tanstack-start-router-manifest:v"

I'm just getting this error trying the alpha.17

13 Replies

solid-orange•4mo ago

yes we are aware of that bug this happens as soon as your client imports anything from react-start/server

rare-sapphireOP•4mo ago

Maybe is because of this? 🤔 but i'm creating first a serverfn so is weird

solid-orange•4mo ago

this import should get stripped off during compilation

rare-sapphireOP•4mo ago

Huh, that the only file where I use something from server

solid-orange•4mo ago

then maybe my assumption was wrong and importing from react-start alone is the issue

rare-sapphireOP•4mo ago

the issue is that docs says that createServerFn is from react-start 😅 so this is like a big issue if is something about documentation to properly handle these cases

rare-sapphireOP•4mo ago

I needed to add this and it starts working on dev

solid-orange•4mo ago

nice! thanks for the update I hope we can get this fixed automatically soon then

rare-sapphireOP•4mo ago

no problem, it's only on dev, and this fix was bright to you by AI, so I'm going to ask it why it did it and how it can be resolved at library level

rare-sapphireOP•4mo ago

Claude says that this can be a good fix to mark them as virtual 😅

rare-sapphireOP•4mo ago

I'm seeing that this is implemented here https://github.com/TanStack/router/blob/alpha/packages/start-plugin-core/src/resolve-virtual-entries-plugin/plugin.ts but maybe the id's have a mismatch

// More robust virtual module handling
export function tanstackStart() {
  return {
    name: 'tanstack-start',
    resolveId(id) {
      if (id.startsWith('tanstack-start-') && id.endsWith('-manifest:v')) {
        return id; // Mark as virtual
      }
    },
    load(id) {
      if (id.startsWith('tanstack-start-') && id.endsWith('-manifest:v')) {
        return generateManifestContent(id);
      }
    }
  }
}

// More robust virtual module handling
export function tanstackStart() {
  return {
    name: 'tanstack-start',
    resolveId(id) {
      if (id.startsWith('tanstack-start-') && id.endsWith('-manifest:v')) {
        return id; // Mark as virtual
      }
    },
    load(id) {
      if (id.startsWith('tanstack-start-') && id.endsWith('-manifest:v')) {
        return generateManifestContent(id);
      }
    }
  }
}

solid-orange•4mo ago

they are virtual modules the issue is the esbuild is not aware of those modules and with the optimizeDeps setting you disabled esbuild for those so this might be the fix we need need to look at it again later

equal-aqua•4mo ago

For me, I added a client.tsx to add Sentry. I'll randomly get this error in dev and have to delete the client.tsx and re-add it.

Gaming

Programming

Could not resolve "tanstack-start-router-manifest:v"

Did you find this page helpful?