波比小金刚
For scalability and compatibility, I should think of a way to replace `history.state`, I will do a search.
i will try to make a pr for it
@molefrog Thanks for your reply. Fully agree to implement related functions in a new repo. similar to the plug-in mechanism to enhance `wouter`, cool!! 🆒 👇 ```js import useLocation from...
may be we can support hash router too. ```js import useLocation from '@wouter/location' // e.g. history default true, but if the browser does not support hash or set history false,...
maybe an interceptor should be supported too in new `useLocation`. ```js const interceptor = (currentPath, nextPath) => { if(confirm('Do you want to leave?')){ return nextPath; } return currentPath; } useLocation({...
@tony-scio hi, 👋 ~ There is currently no best way to convince everyone. I think the simplest implementation is to pass the state through `navigate` ```js const navigate = useCallback(...
I've been busy lately, I'll try to provide an available
what `` component do, actually is: ```js navigate(options.to || options.href, options) ``` then the path `KaiResume.pdf`, no component match this path.