Can I benefit from type safety when using react-router v7 as library mode ?

[QuentinChevance]

Hello,

I would like to know if it is possible to benefit from the new type safety while still using react-router as a library in a SPA ?

[sergiodxa]

The new type-safety features are only for framework mode, what you can do use to use framework mode with ssr: false so you get a SPA using framework mode.

[QuentinChevance]

ssr: false doesn't work out of the box for my use case.
My codebase is pretty large, and refactoring it isn’t straightforward. For example my App component uses keycloak-js which needs to access the window object. This causes issues because the framework attempts to server-render it, resulting in an error since window is not available in that context.
On top of that, I’d need to update all my routes to use clientLoaders for data fetching, even though I’m already using SWR for that.
I gave it a shot, but the process is just too time-intensive. I was hoping there’d be a simpler way to achieve type safety, but it doesn’t seem to exist at the moment.

[sergiodxa]

If you're using SWR and not clientLoaders, what do you need from RR type-safety? The route params? Because the type-safety is mostly to ensure your data from loaders and actions are typed correctly, but with SWR you skip that.

[QuentinChevance]

Yes, we are starting to have more and more route params in my application so that would be the main benefit of the type safety.
I would like to have autocompletion when calling the navigate function for example.

[sergiodxa]

Even with RR type safety the navigate function is not yet typed so you won't get auto completion there

[QuentinChevance]

Ok thank you for you answers