Local development not working after upgrade to newest 1.121
When i run my local setup this is what my console shows:
$ vite dev --port 3000
Generated route tree in 167ms
VITE v6.3.5 ready in 1180 ms
➜ Local: http://localhost:3000/
➜ Network: use --host to expose
➜ press h + enter to show help
And when i visit my dev, the app shows - but it is not interactable....
And then i get this:
Response {
status: 404,
statusText: '',
headers: Headers { 'content-type': 'application/json' },
body: ReadableStream { locked: false, state: 'readable', supportsBYOB: true },
bodyUsed: false,
ok: false,
redirected: false,
type: 'default',
url: ''
}
9 Replies
like-goldOP•3mo ago
Build works fine btw.
And this is my vite.config.ts:
// vite.config.ts
import path from "path"
import tailwindcss from "@tailwindcss/vite"
import { tanstackStart } from "@tanstack/react-start/plugin/vite"
import react from "@vitejs/plugin-react"
import { defineConfig } from "vite"
import tsConfigPaths from "vite-tsconfig-paths"
const ReactCompilerConfig = { target: "19" }
export default defineConfig({
plugins: [
tsConfigPaths({
projects: ["./tsconfig.json"],
}),
tanstackStart({
react: {
babel: {
plugins: [["babel-plugin-react-compiler", ReactCompilerConfig]],
},
},
}),
tailwindcss(),
react(),
],
resolve: {
alias: {
"@": path.resolve(__dirname, "./src"),
},
},
})
exotic-emerald•3mo ago
arent you logging anything?
like-goldOP•3mo ago
Update: I found out that removing the react(), did resolve the issue that the client in local was not responding.
However, the response is still the same.
Response {
status: 404,
statusText: '',
headers: Headers { 'content-type': 'application/json' },
body: ReadableStream { locked: false, state: 'readable', supportsBYOB: true },
bodyUsed: false,
ok: false,
redirected: false,
type: 'default',
url: ''
}
This is from browser console:
Failed to load resource: the server responded with a status of 404 (Not Found)
complex-teal•3mo ago
You also need this :
I also found the react plugin breaks stuff, so you have to enable the compiler the way you've done it above
like-goldOP•3mo ago
Thanks!
I just added it.
Do you also get the weird
Response {
status: 404,
statusText: "",
....}
?
Everything seems to work, but the console throws that weird response.
complex-teal•3mo ago
No I don’t get that. Is your project fresh? Could be something leftover from the template you used?
like-goldOP•3mo ago
I found out that by removing how i get the session (better-auth), the error goes away...
So weird
foreign-sapphire•3mo ago
how are you getting session from better-auth
loader or hook?
or context
like-goldOP•3mo ago
I am query the session inside __root.tsx using context.queryClient that runs a server GET function that uses webrequest() to check my headers for session