The common library built based on wepback, external dependencies do not work properly

[JinHe-PerkinElmer]

Bug report

The common library built based on wepback, external dependencies do not work properly. An error is reported at runtime, it seems that the externals are not correctly parsed from the outside, but from the node_modules of common-lib.

What is the current behavior?

I build a UI common-lib base on webpack, it mainly includes ant-d and react as external dependencies. The webpack configuration is fine and the packaging is successful. But an error is reported during runtime.

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

Wepback externals can work properly.

Other relevant information:
webpack version: ^5.97.1
Node.js version: v22.14.0
Operating System: win10
Additional tools:

My package.json

{
  "name": "os-common",
  "version": "1.0.0",
  "description": "common library of one source spa",
  "author": "",
  "license": "MIT",
  "repository": "os-common",
  "main": "dist/index.js",
  "module": "dist/index.es.js",
  "jsnext:main": "dist/index.es.js",
  "engines": {
    "node": ">=8",
    "npm": ">=5"
  },
  "scripts": {
    "start": "webpack --watch",
    "build": "webpack --env production"
  },
  "peerDependencies": {
    "@microsoft/signalr": "^3.1.27 || ^8.0.7",
    "ag-grid-community": "^33.2.1",
    "ag-grid-react": "^33.2.1",
    "antd": "^5.24.6",
    "file-saver": "^2.0.2",
    "i18next": "^24.2.3",
    "i18next-http-backend": "^3.0.2",
    "md5": "^2.2.1",
    "moment": "^2.24.0",
    "prop-types": "^15.5.4",
    "react": "^19.1.0",
    "react-dom": "^19.1.0",
    "xlsx-style-tw": "^0.15.8"
  },
  "devDependencies": {
    "@babel/core": "^7.15.8",
    "@babel/preset-env": "^7.15.8",
    "@babel/preset-react": "^7.14.5",
    "babel-loader": "^10.0.0",
    "babel-preset-react-app": "^10.0.1",
    "css-loader": "6.8.1",
    "mini-css-extract-plugin": "^2.9.2",
    "sass": "^1.86.0",
    "sass-loader": "16.0.5",
    "style-loader": "4.0.0",
    "webpack": "^5.97.1",
    "webpack-cli": "^6.0.1"
  },
  "files": [
    "dist"
  ],
  "dependencies": {
    "abortcontroller-polyfill": "^1.4.0",
    "react-to-print": "^3.0.5"
  }
}

webpack.config.js

const path = require('path');
const MiniCssExtractPlugin = require("mini-css-extract-plugin");

module.exports = (env) => {
  const isProd = env.production;
  let devtoolSetting = false;
  // if (!isProd) {
  //   devtoolSetting = 'cheap-module-source-map';
  // }
  return {
    mode: isProd ? 'production' : 'development',
    devtool: devtoolSetting,
    entry: './index.js',
    output: {
      filename: 'index.js',
      path: path.resolve(__dirname, 'dist'),
      libraryTarget: 'umd',
      library: 'common'
    },
    plugins: [new MiniCssExtractPlugin({
      filename: 'os-common.css',
    })],
    module: {
      rules: [
        {
          test: /\.jsx?$/,
          exclude: /node_modules/,
          loader: 'babel-loader'
        },
        {
          test: [/\.bmp$/, /\.gif$/, /\.jpe?g$/, /\.png$/, /\.svg$/],
          type: 'asset/inline',
        },
        {
          test: /\.(css|scss)/,
          use: [
            MiniCssExtractPlugin.loader,
            // Translates CSS into CommonJS
            "css-loader",
            // Compiles Sass to CSS
            "sass-loader",
          ],
        },
      ]
    },
    resolve: {
      extensions: ['.ts', '.tsx', '.js', '.jsx'],
    },
    externals: {
      "react": "react",
      "react-dom": "react-dom",
      "i18next": "i18next",
      "i18next-http-backend": "i18next-http-backend",
      "prop-types": "prop-types",
      "moment": "moment",
      "antd": "antd",
      "md5": "md5",
      "ag-grid-community": "ag-grid-community",
      "ag-grid-react": "ag-grid-react",
      "xlsx-style-tw": "xlsx-style-tw",
      "file-saver": "file-saver",
      "@microsoft/signalr": "@microsoft/signalr",
    },
  };
}

Evidence that external dependencies don't work
we can see that the external dependency antd is not resolved from the outside when running, but from the inside of common-lib

Does anyone know what the reason is? @alexander-akait thanks very much.

[alexander-akait]

@JinHe-PerkinElmer Please don't ignore If the current behavior is a bug, please provide the steps to reproduce., I can't see the code, so I can't understand why it happens, can you create reproducible test repo? Thank you and I will look

[JinHe-PerkinElmer]

webpack-externals-demo.zip
@alexander-akait Thanks for you reply.
I write a demo, which contains two applications(main and os-common), you can run it with Node(v22.14.0)
Please refer to the readme.txt for detailed steps. Thanks very much.