[Bug]: ModuleFederation with output.library.type: 'module' (ESM) build doesn't produce a valid module about rspack HOT 8 CLOSED

use experiments.rspackFuture.newTreeshaking

from rspack.

Could you try enable experiments.rspackFuture.newTreeshaking and see whether the problem still exists?

from rspack.

same here

from rspack.

css module also displays abnormally under esm

from rspack.

Could you try enable experiments.rspackFuture.newTreeshaking and see whether the problem still exists?

Doesn't seem to work. Getting the same error as @ckken

If one inspects the remote entry generated, it has the following code at the bottom:

var __webpack_exports__get = __webpack_exports__.get;
var __webpack_exports__init = __webpack_exports__.init;
export { __webpack_exports__get as get, __webpack_exports__init as init };
var __webpack_exports__get = __webpack_exports__.get;
var __webpack_exports__init = __webpack_exports__.init;
export { __webpack_exports__get as get, __webpack_exports__init as init };

Link: https://rollup-plugin-module-federation-pro-git-2c5fbc-madarauchiha-314.vercel.app/rspack/esm/my-remote-entry.js

Update: I manually removed the duplicate lines from my bundle and then everything works.

from rspack.

@MadaraUchiha-314 Is the css module normal after you switch to esm?

from rspack.

fixed css module don`t display!

    //     {
    //       chunkFormat: 'module',
    //       chunkLoading: 'import',
    //       library: {
    //         type: 'module',
    //       },
    //     },

from rspack.

#6010 should fix it, will release the fix soon

from rspack.