someengineer-nordsec
someengineer-nordsec
Please ignore the ugly proof of concept But if you are willing to use redux-thunk   Why the async?...
> > hey, we've found out the hard way, that https://github.com/rt2zz/redux-persist#state-reconciler also plays a big role > > Could you please give more details? https://github.com/rt2zz/redux-persist/blob/master/docs/api.md#type-statereconciler
@ueokande nice work getting extension to load 👍 to playwright team: however, page actions (goto, click, etc...) on `moz-extension://` pages will not work until firefox patches are updated e.g. https://github.com/microsoft/playwright/blob/1277ec99008898cba23c3511d024972e42409963/browser_patches/firefox/juggler/content/JugglerFrameChild.jsm#L41-L43...
This will simply not work if some random package in node_modules uses `@types/chrome`
this will not force it to be a primary resolution in case some third party package installed `@types/chrome`
For now, I'm using `patch-package` ```patch diff --git a/node_modules/chrome-types/index.d.ts b/node_modules/chrome-types/index.d.ts index 4438d02..41e7899 100644 --- a/node_modules/chrome-types/index.d.ts +++ b/node_modules/chrome-types/index.d.ts @@ -1,3 +1,4 @@ +declare module 'chrome-types' { /** * Copyright 2022 Google...
For now I'm using it like this, I'm not a fan of referencing from global scope `globalThis` is for MV3 because SW I had to use `patch-package` 
This would fix #44 , right?
this will not force it to be a primary resolution in case some third party package installed `@types/chrome`