[Module Federation] tree-shaken for shared modules

[fxxjdedd]

webpack.config.js

    new ModuleFederationPlugin({
      exposes: {
        "./Widget": "./src/Widget",
      },
      shared: {
        "lodash-es": {
          import: "lodash-es"
        } 
      },
    })

./src/Widget.js

import { isArray } from 'lodash-es'
export default function Widget() {
  return isArray(...)
}

Very curious about how webpack handles lodash-es tree-shaken here.

[fxxjdedd]

I tried it myself and found that lodash-es was packaged into a chunk. There is no tree-shaken.

This may not be a serious problem, but I am curious what the mechanism is here.

[alexander-akait]

Because you write lodash-es, so other remotes can use any function from lodash-es

[fxxjdedd]

I understand, but it does generate too much content. Even if it may be used by other remotes, it will most likely not use all APIs.