Can Rspack emit import() calls while still bundling the code that's imported?

[dstaley]

I maintain a large library that currently uses Rspack to bundle our browser bundle. This bundle uses dynamic import() calls for code splitting. We'd like to ship a new bundle to be consumed by other bundlers, instead of running in the browser. However, we'd also like to retain the dynamic import() statements so they can be correctly split by the consuming bundler. Currently, even when emitting ESM Rspack will convert these imports to __webpack_require__ calls, which other bundlers are not able to correctly process.

Essentially, given the following index.js:

import a from './a.js';
import b from './b.js';

import('./c.js');

I want index.js to contain the code from a.js and b.js, and a bare import('./c.js').

Furthermore, given the following c.js, I'd expect d.js and e.js to be bundled into the c.js chunk:

import d from './d.js';
import e from './e.js';