[Bug]: Set external extension, compilation error during dependent export

[lzxb]

System Info

System:
OS: macOS 15.0.1
CPU: (8) arm64 Apple M1
Memory: 106.00 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.13.1 - ~/.nvm/versions/node/v20.13.1/bin/node
Yarn: 1.22.22 - ~/.nvm/versions/node/v20.13.1/bin/yarn
npm: 10.5.2 - ~/.nvm/versions/node/v20.13.1/bin/npm
pnpm: 8.15.8 - ~/.nvm/versions/node/v20.13.1/bin/pnpm
bun: 1.1.27 - ~/.bun/bin/bun
Browsers:
Safari: 18.0.1
npmPackages:
@rspack/cli: 1.0.14 => 1.0.14
@rspack/core: 1.0.14 => 1.0.14

Details

Named export is normal, but all exports are incorrect

// Compilation failed
export * from 'test2';
// Compilation successful
export { test2 } from 'test2'

export function test1 () {}

Reproduce link

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

Reproduce Steps

1. rspack.config.js

{
    externals: ['test2']
}

2. packages/test1/index.js

export * from 'test2';

3. Run command

pnpm build

[chenjiahan]

Hi, can you try the modern-module type? It should work:

@fi3ework When will we add documentation for modern-module?

[lzxb]

The exported result is missing

[fi3ework]

Hi, can you try the modern-module type? It should work:

Currently, it does not work with modern-module either. export * is still under track web-infra-dev/rslib#45. I used to try to implement it in modern-module only, but seems it should be fixed as long as output.module = true and module external type used together.

I misread it, only implement in modern-module would be fine.

When will we add documentation for modern-module?

Not in a hurry, many edge cases need to be addressed. We might add it to documentation after Rslib becoming more stable.

[fi3ework]

I will continue working on preserving export * this week. I found a way to use webpack before, but Rspack is not suitable.