Extension/Manifest v3 Browser detection and use of window

[sickpuppysoftware]

Core Library

MSAL.js v2 (@azure/msal-browser)

Wrapper Library

Not Applicable

Description

msal-browser doesn't work as it should when called from a manifest v3 service worker.
I've adapted the extension sample in an attempt to get it working under manifest v3. However I have the following issues depending on where I try to use the library.
Background service worker - The library's browser detection fails as there is no window object in a service worker.
Content script - No access to chrome.identity should library calls fail. I'm also loathed to inject the whole library into every page loaded.

Is there ay way to get the library working with manifest v3?

Source

External (Customer)

[jasonnutter]

@sickpuppysoftware To clarify, this is what you are referring to? https://developer.chrome.com/docs/extensions/mv3/intro/mv3-overview/

Unfortunately, this isn't something we have tested, but we'll add it to our backlog to investigate. We also welcome PRs if you have ideas for specific changes that can be made.

[sickpuppysoftware]

That is what I'm referring to.

[bartlomiejzuber]

@jasonnutter Is there a chance to support that in future ? Our team have exactly the same problem, we use msal for authentication in chrome browser extension which now seems to be impossible due to window not exist inside of service worker. :(

[wolkowsky]

@jasonnutter +1, it's a blocker for us. Will the problem be solved? Could we know ETA?

[nichovski]

Did anyone find a workaround for this issue?

[bartlomiejzuber]

Did anyone find a workaround for this issue?

Kind of yes although I didn't finish it, as a workaround you can use jsdom and assign it to the global.window, additionally you might need to add polyfills for things like Crypto API(https://developer.mozilla.org/en-US/docs/Web/API/Crypto). Keep in mind that this type of workaround will bloat your background(service worker) script bundle significantly.

[Alino]

hi @bartlomiejzuber , did you finish it? Is your solution working well? I wonder if there are not issues with the localStorage when it's kind of polyfilled from jsdom

Does it actually store the data and load it back when you reopen the browser or when the service worker 'resets'? Or are you using your own caching?

[bartlomiejzuber]

hi @bartlomiejzuber , did you finish it? Is your solution working well? I wonder if there are not issues with the localStorage when it's kind of polyfilled from jsdom

Does it actually store the data and load it back when you reopen the browser or when the service worker 'resets'? Or are you using your own caching?

Hi, yeah it worked. Not everything can be pollyfilled by jsdom though. When it comes to local storage you need to implement it using chrome's storage API.