Closed rosskevin closed 1 year ago
I'm going to close this for the moment - I just found a top level route that works and it is leading me to believe we are likely to have a problem in our route config.
Just to close this loop, we did some optimization of an <AppContent/>
and <AppFrame/>
components at the top level with React.memo
and a custom comparator. The condition was inverted and therefore caused the content from the Component
on the new route pushed to not render because it signaled no need to do so.
We have just upgraded an application that has been running successfully for years with
found
.It is now using
react: 18.2.0, found: 1.3.0
and we did switch our build tovite
. I have tried this with and without strict mode based on @jquense comment in #968, but there is no change. I reviewed #961 but the only similarity there is we are both usingvite
. I reviewed the changelog but did not spot anything I am missing.Symptoms:
return
in the location bar renders finefound
to changeAttempts include
strict
mode on/off, add/removehotRouteConfig
, removefound-scroll
(seems to be falling behind), but no changes. Each page works, it will just not render after click of a link (only browser location bar change).I've boiled down my router config to:
I'm still looking but appreciate any pointers.