You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently upgraded an app from @tanstack/start v1.102.5 and now see that in the production build with the 'bun' preset, static assets are no longer served correctly - the server returns a 404. This applies to all assets in the .output/public folder.
The temporary workaround is to use the 'node-server' preset instead and continue to serve the build with bun run.
Which project does this relate to?
Start
Describe the bug
We recently upgraded an app from @tanstack/start v1.102.5 and now see that in the production build with the 'bun' preset, static assets are no longer served correctly - the server returns a 404. This applies to all assets in the .output/public folder.
The temporary workaround is to use the 'node-server' preset instead and continue to serve the build with
bun run
.Your Example Website or App
https://codesandbox.io/p/devbox/6np3x7
Steps to Reproduce the Bug or Issue
The codesandbox is a copy of the 'Start Basic' example with no changes other than the addition of
server: { preset: "bun" }
to app.config.tspnpm build
bun run .output/server/index.mjs
curl -i http://localhost:3000/favicon.png
Expected behavior
The build should continue to function as it did with an earlier version of @tanstack/start.
Screenshots or Videos
No response
Platform
Additional context
No response
The text was updated successfully, but these errors were encountered: