Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support import() local code in extension service worker #1700

Open
hanguokai opened this issue Jan 8, 2024 · 2 comments
Open

Support import() local code in extension service worker #1700

hanguokai opened this issue Jan 8, 2024 · 2 comments

Comments

@hanguokai
Copy link
Member

I know #1585 discussed import() in service worker. Here I am talking about browser extension service worker.

w3c/webextensions#212 Some developers proposed it in WECG. Unlike Web, all code are already locally and offline available in a browser extension. So dynamically import() local code in extension service worker should just like normal javascript behavior, it should not be a problem for extensions.

According to past meeting minutes, browser vendors are basically supportive of it in extension service worker.

I think there should be no objection to supporting import() in extension service worker. Web may also support import() in service worker in the future, but there will definitely be more considerations and requirements.

@tomayac
Copy link
Contributor

tomayac commented Jan 8, 2024

Again looping in @oliverdunk and @patrickkettner, since they may not necessarily monitor this repo.

@ggaabe
Copy link

ggaabe commented Jun 2, 2024

I also support this; Would be a great thing to add. The current restrictions can make developing tooling in extensions that relies on service workers fairly burdensome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants