ESM Module Output #17121
Description
- Consuming build output at build time
-
Build output supports tree-shaking
-
Weird CommonJS modules are wrapped
-
💎
import()is statically analyse-able + import chunks withnew URL()instead of public path How to correctly parse the chunk resources in the library packaged by another webpack in webpack5? #15947 -
💎Nice CommonJS modules are converted to ESM
-
module-wide side-effect information is kept in build output (generate package.json? use
PUREflag?)
-
- Developer Expreience
- Inform (warn) the user about modules that are converted to strict mode
-
delete xin modules should be a build error as code is compiled in strict mode
- Use the platform
- load HMR manifest via
import()+ cache busting (mem leak? is fetch better?) - load HMR chunks via
import() - prefetch chunks/assets via module preload/prefetch +
new URL(...)
- load HMR manifest via
- Consuming build output at runtime
- 💎Live Bindings to entrypoint
- 💎Test case for circular dependency w/ external
- Other
- Preserve CSS Import - (@vankop more information)
- Preserve Reexport from Externals
- Preserve
new URL(),new Worker(). Maybe magic comment for this? - Support
workerChunkLoading: "module"fornodetarget