S
SolidJS•4mo ago
tapsy0

useNavigate causes Make sure your app is wrapped in a <Router />

Hi guys, new to frontend dev and started with solidjs. Now I'm stuck at trying to use useNavigate and don't know what I'm doing wrong. Error message: Make sure your app is wrapped in a <Router /> solidjs/router version: 0.11.2 solidjs version: 1.8.11
No description
No description
5 Replies
Grahf
Grahf•4mo ago
I am thinking that AuthCheck would need to be imported into a function that's wrapped in <Router> or needs to be a Route
tapsy0
tapsy0•4mo ago
AuthCheck will be imported by LoginForm.tsx which will be imported by Login.tsx which is within a <Route> in index.tsx
No description
tapsy0
tapsy0•4mo ago
Any other ideas?
Grahf
Grahf•4mo ago
I have none sorry 😦 other than to make sure it isn't imported into another component that's not wrapped in router....
daan banaan
daan banaan•4mo ago
not sure if you already found the solution to this but I just found out that I get this error whenever I use useLocation()
Want results from more Discord servers?
Add your server
More Posts
Better stacktraces when using SolidJS via a library?Whenever an error occurs within a SolidJS component library, the stacktraces are extremely cryptic. createResource doesn't seem to be catching errors.I have been at this for a while now and can't figure it out. I am calling a fetcher from a createResHow to use ref both inside and outside(parent) component?I have parent component with this code: ```tsx return ( <div> <div class="grid gHi, with latest solid starts ssr title and meta are disappearing and google sees them as empty..Could you please kindly point me to the solution if it exists?How to handle auth with solid-router?Given an app where users have access to additional routes when they are logged in, how to set up theHydration issues when using props.children inside component```js return ( <Router root={(props) => ( <MetaProvider> <QueryClientPrvite:css and postcss creating errors on SSR ?``` 10:56:50 PM [vite] Internal server error: Attempted to assign to readonly property. Plugin: viPlacement of Context Providers and Routes (Router 10.10)I have an existing application which uses several context providers for sharing data between routes.Imported unused variable for a directive seems awkwardI've went through the SolidJS tutorial (https://www.solidjs.com/tutorial/bindings_directives?solved)Vitest supportI was hoping to migrate my TypeScript and SolidJS project template from using Jest to Vitest for a n