Visitar URL original
docs(output): document the futureDefaults module output default by alexander-akait · Pull Request #8396 · webpack/webpack.js.org · GitHub
Skip to content

docs(output): document the futureDefaults module output default - #8396

Merged
alexander-akait merged 1 commit into
mainfrom
docs/future-defaults-module-output
Sep 13, 2026
Merged

alexander-akait merged 1 commit into
mainfrom
docs/future-defaults-module-output

Conversation

@alexander-akait

Copy link
Copy Markdown
Member

Documents the output.module default that webpack/webpack#22088 ships in webpack 5.111.0.

configuration/output.mdx — output.module

  • The default line now also names the module / modern-module library types, which turn the option on without any experiment (fix(config): default output.module to true for module library types webpack#22071, previously undocumented).
  • A new paragraph, badged 5.111.0+, covers the experiments.futureDefaults default: module output wherever the target can read an ECMAScript module, and the three things that keep script output — a target stating it cannot (a browserslist query resolving to engines without module support, or a version below it), a library type read out of a script wherever it is declared, and an explicit output.module. It also spells out that a target saying nothing about modules (web, webworker, a plain node) counts as able to read one.

configuration/experiments.mdx — experiments.futureDefaults

One paragraph naming module output as one of those defaults, with the visible consequence ([name].mjs, output.chunkFormat: 'module', output.chunkLoading: 'import') and a pointer to output.module for the full rule.

Every statement was checked against the merged implementation by resolving real configurations through applyWebpackOptionsDefaults, rather than read off the diff.

lint:prettier, lint:markdown and lint:js pass on both files locally; lint:prose (vale) I could not run here, as it is installed by a GitHub Action rather than npm.


Generated by Claude Code

webpack 5.111.0 defaults `output.module` to true under
`experiments.futureDefaults` wherever the target reads an ECMAScript module,
so both pages now say what turns it on and what holds it back: a target
without module support, a library type read out of a script, or an explicit
`output.module`. The option's own default line also picks up the `module` and
`modern-module` library types, which turn it on without the experiment.
@vercel

vercel Bot commented Sep 13, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
webpack-js-org Ready Ready Preview Sep 13, 2026 2:00pm UTC

Request Review

@alexander-akait
alexander-akait merged commit e47e233 into main Sep 13, 2026
12 checks passed
@alexander-akait
alexander-akait deleted the docs/future-defaults-module-output branch September 13, 2026 14:08

This branch was successfully deployed

1 active deployment
Preview — 09e69628 Deployed Sep 13, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant