react-query-questions
solid-query-questions
table-questions
virtual-questions
router-questions
react-charts-questions
ranger-questions
vue-query-questions
svelte-query-questions
bling-questions
form-questions
angular-query-questions
start-questions
db-questions
start-showcase
router-showcase
📣-announcements
Hosting in Docker with Nitro problems
import { nitro } from 'nitro/vite'
which should be import { nitro } from 'nitro-nightly/vite'
to be aligned with suggested package.
Moreover, after including nitro in vite.config.js I get error:...Request Context's properties are null when defined in Server Entry Point
null
.
```
// src/routes/server-entry-point.tsx...Cannot find package 'h3-v2'
Vitest tanstackStart() plugin conflict
request.headers.get is not a function
Flash of unstyled content (FOUC) issue
Vercel build 404

How to ignore test files in routes directory?
Route file "/home/**/src/routes/index.test.tsx" does not contain any route piece. This is likely a mistake.
Route file "/home/**/src/routes/index.test.tsx" does not contain any route piece. This is likely a mistake.
Do you know any good practice courses to improve tanstack skills?
No client assets in production
Unknown file extension ".css"

Using zod to parse environment
Issues with server routes
const { _splat } = params
-> _splat is undefined and i get typescript errors on that declaration.
- setResponseStatus
is not woring at all...I am getting this error in my tanstack start + nitro v2 deployment on vercel
Error reading routerStream: Invalid state: Controller is already closed error
Query client in loader

How to handle client preferences?
Run code before SSR and CSR in RC
No error upon defining conflicting routes
Environment variables best practices
createServerOnlyFn
to return an environment variable so that it's not accidentally leaked to the client. However, in another section (https://tanstack.com/start/latest/docs/framework/react/environment-variables) it says that env variables aren't even accessible in client code unless the name is prefixed with VITE_
.
I'm struggling to understand in which circumstance each solution is supposed to be used, as from my understanding they both result in the same end functionality of the variable being withheld from the client bundle. Can anyone shed some light on this and help me understand the specific cases in which one approach should be preffered?
Thanks!...