I used theRouter CLI, created a
"router:generate": "tsr generate", in thepackage.json so I can use it in my build process.

@SeanCassiere has anything changed since the last year? Still the same guidance?

I'll probably create a FAQ section and chuck this in there.

FAQ would be nice! A counterpoint I can offer is that dependencies are also essential to your application running and would fail typecheck if not installed, yet we don't keep them in git. Even more similar, I work on codegen (see my profile) and the same question arises there. I went from yes to no on the same question. It's not that difficult to generate everything that's needed onpostinstall or with a Vite plugin – you're doing that already anyway! In fact, I looked at the TanStack Router Vite plugin when working on mine, so I suspect it might just work™. A practical argument I hear for not committing the generated files is it makes switching between branches easier as there won't be any conflicts.

The FAQ is up -https://tanstack.com/router/latest/docs/framework/react/faq

@mrlubos, I get what you mean. My only argument against the conflict point is, that this isn't like yourpackage-lock where some trailing commas pretty much always guarantee a conflict. So conflicts really should be at the minimum. The route tree also serves as an accurate point-in-time snapshot as to what TanStack Router would've used at runtime.

@SeanCassiere please update the same over here as well -https://tanstack.com/start/latest/docs/framework/react/guide/routing#:~:text=You%20may%20gitignore%20this%20file%2C%20since%20it%20is%20a%20build%20artifact.

What's the point of building if typecheck failed? It should ideally be

"build":"tsc --noEmit && vite build"

The point is that tsc will always fail if there's no generated route-tree file, which I have git ignored.