Is it possible to access location.state from a clientLoader?

[lockr7]

I saw remix-run/remix#8243 which makes sense but now that clientLoaders exist, curious if there's a way to access this

[sergiodxa]

Using window.history.state in a clientLoader or clientAction should be possible to access the location.state

[misha-erm]

@sergiodxa I found that window.history.state lags behind. After I useNavigate with state window.history.state inside loader misses the properties I set. But they are present if I check state with useLocation. Is it something expected or should I dig deeper and create the issue?

[jbojcic1]

@misha-erm were you ever able to solve that? I have similar issue described here remix-run/remix#10721

[misha-erm]

unfortunately I don't remember :(
I think I implemented my feature in a different way and switched to "global" state variable, e.g.

feed-positions.tsx


const feedPositions: Map<string, GridStateSnapshot> = new Map();

export const hasGridFeedPosition = (key: string) => feedPositions.has(key);
export const removeGridFeedPosition = (key: string) =>
  feedPositions.delete(key);
  
export const setFeedPosition = (gss: GridStateSnapshot) => {
    feedPositions.set(key, gss);
  };

and inside loader:

const clientLoader = () => {
  if (hasFeedPosition(history.state.key)) {
    ...
  } 
}

[misha-erm]

@jbojcic1 not sure but maybe you should use HashRouter if you need your loaders to be triggered on hash change