Re: [w3c/ServiceWorker] Top-level await integration for ServiceWorkers running modules (#1407)

The current proposed solution would fork the language's two parse goals - Script and Module - into three: Script, Module, and ModuleWithoutAwait (ie, "Service Worker Module"). This will create an enormous burden on tooling - linting/static analysis and transpilers in particular - an ecosystem which has already endured much burden by the addition of the Module parse goal.

I think that any syntax that parses in a Module should parse in every Module, and I'm not clear on why this is a necessary solution for Service Workers. Can someone tl;dr me the above very long thread and help me understand why creating a third parse goal for the JS language is a necessary step here?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1407#issuecomment-533829513