Repository navigation
[web] Support content-hashed entrypoint filenames (--web-content-hash) #191914
Description
Summary
Part of umbrella issue #149031.
Support content-hashing compiled top-level JavaScript and WebAssembly entrypoint binaries (main.dart.<hash>.js, main.dart.<hash>.wasm, main.dart.<hash>.mjs, and associated .js.map / .mjs.map files) when building Flutter Web with --web-content-hash.
Scope & Requirements
- Add
--web-content-hashflag descriptor inWebOptions(flutter_tools). - Compute SHA-256 content hashes of compiled entrypoints in
Dart2JSTargetandDart2WasmTarget. - Dynamically inject the resolved hashed entrypoint paths into
_flutter.buildConfiginsideflutter_bootstrap.js. - Preserve unhashed
main.dart.wasm.mapto maintain WebAssembly binarysourceMappingURLcustom section integrity. - Prune stale hashed entrypoint files from
build/web/across repeated builds. - Fast-fail build if legacy
web/index.htmlcontains direct<script src="main.dart.js">tags or deprecatedFlutterLoader.loadEntrypointcalls.
Pull Request
In flight in #190153.
Activity
feat(web): support --web-content-hash for entrypoint files (flutter#1…
fix(web): hide --web-content-hash until content hashing is complete (f…
github-actions commentedon Sep 24, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.