Yago Pérez Vázquez

If I run it with the watchAll option to false it works ``` npm test -- --coverage --watchAll=false ```

Mmmm no idea. When I develop I really don't want the application being instrumented and reporting coverage all time so I'm only generating the report when need to check it

Designs! => https://www.figma.com/file/RqEZSC19sJRH6rbOFm6kxj/Assistance-pop-ups?node-id=222%3A2298

> Providing a bit more info for the issue mentioned above, If I provide address book safe permissions for one of the testing apps and then choose to remove the...

A button for remove the entry in the settings is fine for me @liliiaorlenko, @dasanra ?

Yep I would add the bin icon (or Remove Permission link) just in the links row

RFC: https://docs.google.com/document/d/1hHjoHnwjhq3xtyBuIogFkglS9f6GLsbZTbqZsxduVNE/edit

Beautiful @leonardotc thanks!. I think you need to pull from the target branch for fixing the failing tests

Same is happening to us. We are developing a component library for our applications and we are not able to access the theme from the components in the library. All...

This is due to NPM v7+ installing peerDependencies [by default](https://github.com/npm/rfcs/blob/main/implemented/0025-install-peer-deps.md). This is not the case with previous versions NPM `[email protected]` has a peer using ethers 5.4.0. This should be addressed...