John Blackbourn
John Blackbourn
Alternatively we could bundle asset-loader with a different namespace, but yes I would prefer option 1.
Nope there hasn't been any work done on this 👍
It's in the `.nvmrc` file but nowhere else. The whole Node setup needs updating to Node 20 too.
As Rob pointed out, the GitHub Actions workflow for the build is not failing either, everything is green. Needs looking into.
It seems [the a11y issues with React Select are quite pervasive](https://github.com/JedWatson/react-select/issues/2456). While it is fully keyboard accessible, its controls are not particularly intuitive and there are many ARIA issues relating...
Mentioned by Thorsten is the built-in tag component in Gutenberg, `FlatTermSelector`. Needs looking in to.
Thanks for the review Thorsten, this was valuable. The **tl;dr** answer to most of the "Why?..." questions is that I hadn't gotten around to revisiting a lot of the code...
I don't think there's anything left to do here other than testing and, as you pointed out, to get any other providers updated as necessary.
Other options: * https://github.com/bigbite/wp-cypress * Storybook
* [UnexpectedJS](https://css-tricks.com/react-component-tests-for-humans/)