GoogleChromeLabs/worker-plugin

[question] Support service workers?

Open

Aperta il 1 ott 2018

Vedi su GitHub
 (3 commenti) (3 reazioni) (0 assegnatari)JavaScript (1908 star) (88 fork)batch import
enhancementgood first issuehelp wanted

Descrizione

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?

Guida contributor

Tech stack
javascript
Dominio
frontendtooling
Tipo issue
feature
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 hours
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
needs maintainer response
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
mostly clear
Prerequisiti
Basic knowledge of web workersUnderstanding of service workers
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
50
Direzione di ricerca
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.