T
TanStack•11mo ago
rising-crimson

Is it possible to trace what triggered "Generating routes" messages on dev server start?

When starting the dev server, we see the Generating routes message twice. Sometimes it also triggers Vite to re-optimize dependencies Re-optimizing dependencies because vite config has changed. Is there a way to enable debug logs or something that will tell me what triggers the double output? Here's an example output on startup (we're not running tanstack start, just hand rolled Vinxi) 
vinxi v0.4.3
vinxi found vinxi app config in vite.config.ts
vinxi starting dev server

♻️  Generating routes...
Re-optimizing dependencies because vite config has changed
Re-optimizing dependencies because vite config has changed (x2)
✅ Processed routes in 328ms

♻️  Regenerating routes...
Re-optimizing dependencies because vite config has changed (x3)
✅ Processed routes in 180ms

  ➜ Local:    http://localhost:5173/
  ➜ Network:  use --host to expose
vinxi v0.4.3
vinxi found vinxi app config in vite.config.ts
vinxi starting dev server

♻️  Generating routes...
Re-optimizing dependencies because vite config has changed
Re-optimizing dependencies because vite config has changed (x2)
✅ Processed routes in 328ms

♻️  Regenerating routes...
Re-optimizing dependencies because vite config has changed (x3)
✅ Processed routes in 180ms

  ➜ Local:    http://localhost:5173/
  ➜ Network:  use --host to expose
2 Replies
adverse-sapphire
adverse-sapphire•11mo ago
no tracing available right now, could be added. can you reproduce this in a minimal example?
rising-crimson
rising-crimsonOP•11mo ago
I wish I had the time to dig deeper into this, but I'm on partial parental leave for the next couple of months and only working two days a week, so I really gotta make the most of it when I'm active. Not much time for polish like this, and our repo is quite large so pruning it down to minimal repro would probably take a good chunk of time out of my day 😬 Was hoping there was a quick way to see if there was a certain file change that triggered the regeneration. For now I just muted TSR logs completely, which feels unsatisfactory, but is good enough 😅

Did you find this page helpful?