Move devtools code to use mjs files, rather than defining sourceType for ESLint
Categories
(DevTools :: General, task)
Tracking
(firefox108 fixed)
| Tracking | Status | |
|---|---|---|
| firefox108 | --- | fixed |
People
(Reporter: standard8, Assigned: standard8)
References
(Blocks 2 open bugs)
Details
Attachments
(2 files, 1 obsolete file)
With the transition to using ES modules rather than JSMs getting started, we are now using the .mjs extension for those files.
We'd like to transition our content code that is using modules to use the .mjs extension as well - the primary gains of this are that we a) don't need to manually specify sourceType: module for ESLint, b) this gives a visual distinction to developers that the file is a module rather than a regular JavaScript file.
This bug is for the devtools files.
|
Assignee | |
Comment 1•2 years ago
|
||
|
||
Updated•2 years ago
|
|
|
Assignee | |
Comment 2•2 years ago
|
||
When we initially enabled the import checker, we enabled a set of rules that seemed reasonable.
However import/no-anonymous-default-export seems to strict for various cases around mozilla-central, and I don't
think it adds too much, so lets disable for now.
|
|
Assignee | |
Comment 3•2 years ago
|
||
Depends on D161263
|
|
||
Updated•2 years ago
|
|
||
Comment 5•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/0f42421d5fd1
https://hg.mozilla.org/mozilla-central/rev/c4b9d89c2325
Description
•