Support import() local code in extension service worker
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
I know #1585 discussed import() in service worker. Here I am talking about browser extension service worker.
https://github.com/w3c/webextensions/issues/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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #1585, the linked WECG issue #212, and the 2022-05-26 meeting minutes. Compare their discussion of import() in extension service workers with this request, then determine the specification changes and interoperability expectations needed for support. Done means the desired extension-service-worker behavior and requirements are resolved in the ServiceWorker specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100