Error in production but not caught by linter via pnpm build

Which project does this relate to?

Create Tanstack App

Describe the bug

I discovered a bug because I was trying to figure out why my code was building and deplying without errors then upon visiting the deployed website getting the response back from the url in return.

{
  "error": true,
  "url": "https://tanstack-start-deployment-bug.vercel.app/",
  "statusCode": 500,
  "statusMessage": "Server Error",
  "message": "Server Error"
}

I made a repo to demonstrate the issue

https://github.com/remusris/tanstack-start-deployment-bug

below is the deployment url

https://tanstack-start-deployment-bug.vercel.app/

Basically if you export a const from the a route into some component this will trigger the error in deployment.

If you look at the ComponentWithImportedZod.tsx file that is culprit of the issue

https://github.com/remusris/tanstack-start-deployment-bug/blob/master/src/components/ComponentWithImportedZod.tsx

If this is non an error please let me know what I'm doing wrong.

Your Example Website or App

https://tanstack-start-deployment-bug.vercel.app/

Steps to Reproduce the Bug or Issue

Export a const from a file inside of routes into a component outside of routes. In this case it was a zod schema for validating searchParams

Expected behavior

The user does not get any build errors or deployment errors but once the URL is live all you get in response is

{
  "error": true,
  "url": "https://tanstack-start-deployment-bug.vercel.app/",
  "statusCode": 500,
  "statusMessage": "Server Error",
  "message": "Server Error"
}

https://tanstack-start-deployment-bug.vercel.app/

Screenshots or Videos

Check out the url below

https://tanstack-start-deployment-bug.vercel.app/

Platform

Google Chrome | 140.0.7339.128 (Official Build) (64-bit) (cohort: Stable)
Revision | 36aa3351631d175ee5346a1aaf74ef5d49abe308-refs/branch-heads/7339@{#1850}
OS | Windows 11 Version 24H2 (Build 26100.6584)

Additional context

No response

Commencez par src/components/ComponentWithImportedZod.tsx dans le dépôt de reproduction lié, puis exécutez pnpm build et comparez son résultat avec la réponse Vercel déployée. Déterminez pourquoi l’exportation d’un const depuis une route vers un composant externe produit une erreur 500 après le déploiement ; le travail est terminé lorsque la reproduction ne se déploie plus avec cet échec ou que le problème est signalé pendant le build.