Christian Engel
Christian Engel
It doesnt make sense sorting query parameters, if they are turned into an object. Objects don't have a fixed key order by design. If you need a custom solution for...
The `useQueryParams()` hook is completely standalone. Only for convenience, its also included into calls to `navigate()` but this is _not_ routing related. You can ignore that feature of hookrouter and...
I see. Let me think about it.
Hey there - I will take a look into it. Had very few spare time recently but am now back to fix some bugs and prepare v2 of hookrouter.
I have nearly zero free time to work on the project, but its not dead.
This seems to be a bug, indeed. As a workaround, can you try to redirect to `./inbound` instead of `/inbound`? Maybe this helps.
I honestly have no idea how those files ended up there. I did not use TS to create hookrouter, so no idea what generated them 🤔 However - I am...
I had a similiar error before in a production build. My reason was that I forgot to upload one of the bundle files to my webserver and its contents were...
Working on 2.0 right now and I am thinking about this but am not sure about all of that. The 302 is straightforward. I dare to say every call to...
I think you require React 17.x for your app while hookrouter is built for react 16. Therefore you have a dependency conflict.