Avindra Goolcharan

All you need to do is install `atom-keyboard-macros-vim` now. The author merged in `vim-mode-plus` support https://github.com/JunSuzukiJapan/atom-keyboard-macros-vim/commit/4804fb4a67a7f325814d83f470225260912c1364

`linaria` specifies `react >=16`: https://github.com/callstack/linaria/blob/4ee73ae362ca775999bf71c93279db5268108d13/packages/react/package.json#L51 Maybe it's coming from another dependency ? Specific to `npm`, you may be able to bypass the problem with `--legacy-peer-deps`, which I've had to use...

Still having this issue. `QT_SCREEN_SCALE_FACTORS=1` doesn't help

Ah, setting `QT_SCALE_FACTOR=1` works for me.

Firefox hasn't implemented seeking. Chromium did it already. Relevant bugs: * https://bugzilla.mozilla.org/show_bug.cgi?id=1353652 * https://bugzilla.mozilla.org/show_bug.cgi?id=1615790 * https://bugzilla.mozilla.org/show_bug.cgi?id=1634192 * https://bugzilla.mozilla.org/show_bug.cgi?id=1659199

The premise of this library is wrong/ obsolete. With the latest react router the hooks give you the values you need. -- Sent from Mobile

With `useSelector`, you can pass params as everything is in the same scope. Say for example you had a query param named `userId` that you wanted to use in your...

If you still have a lot of class-based components (which BTW you should get rid of to keep on track with latest react)... then you can use `withRouter` to get...

> this looks like workaround Happy to disagree. FWIW, I removed a hundred or so of these `connected` router hacks, dropped `connected-react-router` and the code became much clearer in a...

If you use `withRouter`, everything is done within the selector (using `ownProps` to access router data). As you noted, with the `useParams` approach, some of the code gets moved to...