Closed Bug 1779629 Opened 2 years ago Closed 1 month ago

ESMify mozjexl.jsm

Categories

(Firefox :: Messaging System, task, P2)

task
Points:
8

Tracking

()

RESOLVED FIXED
125 Branch
Tracking Status
firefox125 --- fixed

People

(Reporter: dmosedale, Assigned: mconley)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Whiteboard: [esmification-timeline])

Attachments

(2 files, 1 obsolete file)

mozjexl.js / mozjexl.jsm need to be replaced by an ESM module. That file is moving to being generated in https://github.com/mozilla/mozjexl.

I think the fast path here is likely to be to upgrade that repo to a new version of webpack that supports generating ES modules. Or if that turns out to be a pain, switching to rollup or somesuch.

Priority: -- → P2
Attached file GitHub Pull Request
Assignee: nobody → standard8

I'd guess it will make sense to land this as part of bug 1778535.

Assignee: standard8 → nobody
Whiteboard: [esmification-timeline]
Points: --- → 8

An alternative here would be to do a "simple" conversion of the existing mozjexl in-tree, i.e. this.mozjexl= -> export var mozjexl =, and strip EXPORTED_SYMBOLS.

This would unblock this bug and esm-ification, though would mean that there would be a couple of extra steps next time an import happened from the repository - however, given that doesn't seem to happen often, maybe that isn't much of an issue.

Attachment #9334137 - Attachment is obsolete: true
Assignee: nobody → mconley
Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c07676719b31
Hand-convert mozjexl.js to an ESM. r=dmose,Standard8
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 125 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: