You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: