Closed Bug 1797686 Opened 3 years ago Closed 3 years ago

Migrate toolkit/modules/subprocess to ES modules

Categories

(Toolkit :: Async Tooling, task, P1)

task

Tracking

()

RESOLVED FIXED
108 Branch
Tracking Status
firefox108 --- fixed

People

(Reporter: standard8, Assigned: standard8)

References

Details

(Whiteboard: [esmification-timeline])

Attachments

(3 files)

As part of the ongoing process, we should migrate the subprocess modules to ES modules.

The current set up assumes that all files in the subprocess directory are chrome workers. This causes various globals to be assumed to be present when they are not.
Also stop using import-globals-from in preparation for migration to ES module.

Severity: -- → S3
OS: Unspecified → All
Priority: -- → P1
Hardware: Unspecified → All
Pushed by mbanner@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b764f2133770 Fix chrome worker ESLint definitions for toolkit/modules/subprocess. r=kmag https://hg.mozilla.org/integration/autoland/rev/a70d2c6faaad Esmify toolkit/modules/subprocess modules. r=kmag https://hg.mozilla.org/integration/autoland/rev/68aba44456ff Convert subprocess import consumers to import ES modules directly. r=kmag,application-update-reviewers,bytesized
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: