Build: use .mjs extensions for build-module files #74348
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jsnajdr
added
[Type] Build Tooling
jsnajdr
requested review from
a team,
DAreRodz,
adamsilverstein,
adamziel,
ajitbohra,
atimmer,
dmsnell,
draganescu,
ellatrix,
fabiankaegy,
gigitux,
kevin940726,
luisherranz,
mmtr,
nerrad,
ntsekouras,
ntwb,
oandregal,
peterwilsoncc,
swissspidy and
talldan
as code owners
github-actions
bot
added
[Package] Element
github-actions
bot
added
[Package] Patterns
jsnajdr
force-pushed
the
update/mjs-extensions
branch
from
e948281 to
3ec5cdd
Compare
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
jsnajdr
force-pushed
the
update/mjs-extensions
branch
3 times, most recently
from
6651f24 to
cca1e06
Compare
|
Size Change: 0 B Total Size: 3.08 MB ℹ️ View Unchanged
|
jsnajdr
force-pushed
the
update/mjs-extensions
branch
from
cca1e06 to
86a02be
Compare
jsnajdr
force-pushed
the
update/mjs-extensions
branch
from
daa5a72 to
182eeee
Compare
Member
Author
|
@manzoorwanijk @aduth @youknowriad This is now ready as a followup to #73822. It should fix the issues that Jetpack encounters when trying to use the I had to give up on Instead, the published files in After some additional fixes here and there, renaming a few files (mostly stylelint) from One major package I found that uses this convention is stylelint. No |
manzoorwanijk
approved these changes
Jan 7, 2026
Member
manzoorwanijk
left a comment
manzoorwanijk
left a comment
There was a problem hiding this comment.
This makes more sense, and I agree that the explicit extension regardless of the type field in the package.json makes it more reliable, robust, and portable.
ciampo
pushed a commit
that referenced
this pull request
Jan 7, 2026
* Build: output .mjs extensions for ESM build * ESLint resolver: map .mjs files to .js source * Theme: add .mjs extensions to generated files and stylelint plugins * Components: rename stylelintrc to .mjs * package.json files: remove type:module, .mjs exports * Add changelog entries
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attempt to fix the CJS build issues described in #73822 (comment). The plan is to:
type: modulefrompackage.jsonfiles, because that enables strict Node.js compat in esbuild (Double wrapping when converting esm to cjs evanw/esbuild#2623) which makes it practically impossible to usedefaultexports while producing CJS versions of packages.type: moduleuse the.mjsextension for all ESM files. The idea is that we don't use.jsextensions, for whichtype: moduleprovides the default format, but we always specify the module format explicitly, with the.cjsor.mjsextension.Let's see what CI checks think about this.