undefined | Better HN

0 pointscaladin3y ago0 comments

One interesting consequence of this is that Google's own javascript api client will no longer work with MV3 and there are apparently no plans to ever make it work.

See https://github.com/google/google-api-javascript-client/issue...

Chromium bug marked WONTFIX: https://bugs.chromium.org/p/chromium/issues/detail?id=116445...

Updated readme: https://github.com/google/google-api-javascript-client/blob/...

So effectively this means extensions on MV3 can't easily access Google apis, which is quite unfortunate since Chrome extensions in particular made Google authentication super straightforward (piggybacking off of chrome's built-in google authentication). If someone knows a better way I'd love to hear it.

I believe the reason that the current incarnation of the javascript library won't work is because it modifies the dom to add script tags to fetch and run the api library (or components of it), which is specifically what MV3 will disallow AFAIK.

0 comments

1 comments · 1 top-level

somehnacct37573y ago

MV3 nukes pretty much every third party js in existence.

If the lack of a DOM doesn't do it, the extremely spartan service worker environment will take it out. Did they use XHR? SW only supports fetch. Did they use the window global? Don't have one of those either.

It's the stone ages right now. If you want to integrate with a third party in MV3 you are building a fetch wrapper around their raw HTTP API. Google thinks this is production ready

j / k navigate · click thread line to collapse