GoogleChromeLabs/worker-plugin

[question] Support service workers?

Open

#7 opened on Oct 1, 2018

View on GitHub
 (3 comments) (3 reactions) (0 assignees)JavaScript (1,908 stars) (88 forks)batch import
enhancementgood first issuehelp wanted

Description

I know this is specific to web workers, however I think this could be adapted to work for service workers. I was looking to create a separate plugin but the code would be mostly the same.

Looks like it scans the AST for a keyword (Worker) and generates an entry for the referenced file.

// web worker
new Worker('./foo.js', { type: 'module' })

// service worker
navigator.serviceWorker.register('./foo.js', { type: 'module' })

Could it be adapted to be more generic or am I missing something specific this does for web workers?

Contributor guide

Tech stack
javascript
Domain
frontendtooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic knowledge of web workersUnderstanding of service workers
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Examine how the plugin currently scans AST for `Worker` keyword to generate entry points for web workers. Then investigate `navigator.serviceWorker.register` calls and determine if a similar AST scanning pattern can be applied. Check the plugin's source code (likely index.js) for the existing logic and consider whether a generic or configurable approach is feasible. Engage with maintainers to clarify desired API and scope.