ESM Module Output

[TheLarkInn]

• Consuming build output at build time
  • Build output supports tree-shaking
  • Weird CommonJS modules are wrapped
  • 💎import() is statically analyse-able
  • 💎Nice CommonJS modules are converted to ESM
  • No additional runtime code
  • module-wide side-effect information is kept in build output (generate package.json? use PURE flag?)
• Developer Expreience
  • Inform (warn) the user about modules that are converted to strict mode
  • delete x in 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 HMT chunks via import()
  • prefetch JS chunks via module preload/prefetch + new URL(...)
• Consuming build output at runtime
  • 💎Live Bindings to entrypoint
  • 💎Test case for circular dependency w/ external
• Other
  • Import chunks with new URL() instead of public path How to correctly parse the chunk resources in the library packaged by another webpack in webpack5? #15947
  • Preserve CSS Import - (@vankop more information)
  • Preserve Reexport from Externals
  • Preserve new URL(), new Worker(). Maybe magic comment for this?
  • Support workerChunkLoading: "module" for node target

[alexander-akait]

Related #2933, I will go through everything and add what we might have missed

[webpack-bot]

This issue had no activity for at least three months.

It's subject to automatic issue closing if there is no activity in the next 15 days.

[zackarychapple]

bumping to keep from closing.

[0xUgochukwu]

hey, i'm intrested in working on this during the summer at GSoC