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
currently in dev, vite discovers deps lazily as routes are navigated, which triggers re-optimization and a full reload (visible flicker). the plugin already knows every route file, so it could feed them to vite's dep scanner upfront.
no more mid-session re-optimization flickers after this.
could @react-router/dev/vite just set these by default from the resolved route config? feels like something the plugin is uniquely positioned to do, and a nice ootb dx win.
happy to open a pr if it'd help, lmk if the direction sounds right first :)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
currently in dev, vite discovers deps lazily as routes are navigated, which triggers re-optimization and a full reload (visible flicker). the plugin already knows every route file, so it could feed them to vite's dep scanner upfront.
workaround in
vite.config.ts:no more mid-session re-optimization flickers after this.
could
@react-router/dev/vitejust set these by default from the resolved route config? feels like something the plugin is uniquely positioned to do, and a nice ootb dx win.happy to open a pr if it'd help, lmk if the direction sounds right first :)
Beta Was this translation helpful? Give feedback.
All reactions