[Bug]: modern-module library compilation mode not exported properly

[lzxb]

System Info

System:
OS: macOS 15.0.1
CPU: (8) arm64 Apple M1
Memory: 125.64 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.9.0 - ~/.nvm/versions/node/v22.9.0/bin/node
Yarn: 1.22.22 - ~/.nvm/versions/node/v22.9.0/bin/yarn
npm: 10.8.3 - ~/.nvm/versions/node/v22.9.0/bin/npm
pnpm: 9.13.2 - ~/.nvm/versions/node/v22.9.0/bin/pnpm
bun: 1.1.27 - ~/.bun/bin/bun
Browsers:
Safari: 18.0.1
npmPackages:
@rspack/cli: 1.1.4 => 1.1.4
@rspack/core: 1.1.4 => 1.1.4

Details

Source code

Compile code

Reproduce link

https://github.com/lzxb/rspack-externals-error

Reproduce Steps

pnpm i
pnpm build

[lzxb]

If mode equal to production , It is ok。

[fi3ework]

The reason of the verbose output is due to lacking the following configurations:

  experiments: {
    outputModule: true,
+    rspackFuture: {
+      bundlerInfo: {
+        force: false,
+      },
+    },
  },
  optimization: {
    minimize: false,
+   concatenateModules: true,
  },

1. manually enable concatenateModules in development mode, as it's the premise of modern-module. I think it's reasonable to check it's enabled before build by default.
2. disable bundlerInfo to avoid unneed debug info.

[lzxb]

I use modern-module, which can cause many module compilation errors. Canmodule support export *?

[lzxb]

My Config

Source code

Output

[lzxb]

The content output here has lost its export.

[fi3ework]

I use modern-module, which can cause many module compilation errors.

Could you provide the error so we can fix it?

Canmodule support export *?

No.

[fi3ework]

A reproduce repository please? It is hard to reproduce via a screenshot.

[lzxb]

A reproduce repository please? It is hard to reproduce via a screenshot.

I updated code.
https://github.com/lzxb/rspack-externals-error

[lzxb]

[fi3ework]

Same as web-infra-dev/rslib#316.

Workaround for now it's to use two splitted build process.

[fi3ework]

Specify different layer (https://rspack.dev/config/experiments#experimentslayers) for each entry is also a workaround.