Michael Carter

Thanks for the PR. I'm not seeing the README changes you mentioned. Anyway, this looks like a great feature. I like the addition of `yargs`. It was my intention to...

I like your changes... but I would like to move the command specific yargs to the command itself instead of the cli. So in each command, export a function that...

I figure commands that are added by the user are either done via file system path (so local commands) or npm install -g (install to global). The onus is on...

Have any of you that are complaining attempted to solve the issue on your own? It's not a matter of "authors refuse to fix this"... but that they have limited...

How do you know? If you solve the problem others are having, I'm sure they'll be happy to consider it. And even if they don't at least your app will...

Also, remember that you can *navigate* a link by focusing it and pressing Enter. So a "click" is not required.

Updating search params is considered navigation, so re-rendering seems appropriate. If you need to maintain state, then I suggest using `location.hash`, as that's considered local state, and should not trigger...

Have you looked into `location.state`? This allows you to store state per location without affecting the URL. https://github.com/remix-run/history/blob/main/docs/api-reference.md#locationstate

Use the `useNavigation` hook at your top-level route. This will give you the state of all loaders/actions in your app. https://reactrouter.com/en/main/hooks/use-navigation

I believe that hook is going to be renamed to `useNavigation` to prevent confusion with React's `useTransition`. https://beta.reactrouter.com/en/dev/hooks/use-navigation