InternationallyRanked
InternationallyRanked
SSolidJS
Created by InternationallyRanked on 5/5/2025 in #support
SolidStart clientside routing issue
I was trying to be fancy with an unsubscribeAll function🤦‍♂️. Just moving it to a closure works fine. Nice.
8 replies
SSolidJS
Created by InternationallyRanked on 5/5/2025 in #support
SolidStart clientside routing issue
Yes, this solves it! Thank you so much.
8 replies
SSolidJS
Created by InternationallyRanked on 5/5/2025 in #support
SolidStart clientside routing issue
Oh, I just figured out another piece of the puzzle. If I comment out my getClient() tRPC code and I just use it without establishing a socket anywhere then the routing works fine. Is this potentially broken? Or some kind of limitation?
8 replies
SSolidJS
Created by InternationallyRanked on 5/5/2025 in #support
SolidStart clientside routing issue
Actually I just discovered that strangely enough if you go to the users page first and navigate to any other page it actually works. Further navigation doesn't work.
8 replies
SSolidJS
Created by InternationallyRanked on 5/5/2025 in #support
SolidStart clientside routing issue
That was actually my first instinct, to wrap it like this:
export default function App() {
return (
<Router
root={props => (
<Layout>
<MetaProvider>
<Title>SolidStart</Title>
<Suspense>
{props.children}
</Suspense>
</MetaProvider>
</Layout>
)}
>
<FileRoutes />
</Router>
);
}
export default function App() {
return (
<Router
root={props => (
<Layout>
<MetaProvider>
<Title>SolidStart</Title>
<Suspense>
{props.children}
</Suspense>
</MetaProvider>
</Layout>
)}
>
<FileRoutes />
</Router>
);
}
But it didn't work either which is why I modeled it after the auth-unstorage project with (root).tsx The way I did. I actually had this commented out in there just to show I had already tried it. I think I've somehow broken the clientside router and I cant figure out what's causing it.
8 replies