🐛[BUG] Module not found: Error: Package path ./helpers/esm/regeneratorRuntime is not exported from package \@ant-design\pro-list\node_modules\@babel\runtime (see exports field in \node_modules\@ant-design\pro-list\node_modules\@babel\runtime\package.json)

[stantoxt]

🐛 bug 描述

当引入 @ant-design/pro-list ,编译报错
Module not found: Error: Package path ./helpers/esm/regeneratorRuntime is not exported from package @ant-design\pro-list\node_modules@babel\runtime (see exports field in \node_modules@ant-design\pro-list\node_modules@babel\runtime\package.json)

查看对应目录下的@babel\runtime\package.json 确实里面没有 regeneratorRuntime
但是 node_modules@babel\runtime\package.json 下面有 regeneratorRuntime

不知道是什么原因？和这个有关系吗？

babel/babel#14538

dvajs/dva#2493

📷 复现步骤

🏞 期望结果

💻 复现代码

[github-actions]

以下的 Issues 可能会帮助到你 / The following issues may help you

• [🐛[BUG] Module not found: Error: Package path ./helpers/esm/regeneratorRuntime is not exported from package \@ant-design\pro-list\node_modules\@babel\runtime (see exports field in \node_modules\@ant-design\pro-list\node_modules\@babel\runtime\package.json) #5272][🐛[BUG] Module not found: Error: Package path ./helpers/esm/regeneratorRuntime is not exported from package @ant-design\pro-list\node_modules@babel\runtime (see exports field in \node_modules@ant-design\pro-list\node_modules@babel\runtime\package.json)][100%]

[nicolo-ribaudo]

Hi! Babel maintainer here. This error looks different from the linked dva issue; I'll take a look later today.

[stantoxt]

@nicolo-ribaudo I copied manually root node_modules/@babel/runtime folder to all ant-design-procomponents node_modules and it successfully compiled. Maybe this is not a bug, but I don't know why, I cant find any issue about, if this is about the network problem.

[stantoxt]

My project worked fine,before yarn add ant-design/pro-list.According to the error, there is no config about regeneratorRuntime in node_modules@ant-design\pro-list\node_modules@babel\runtime\package.json. I want to know the problem

[nicolo-ribaudo]

Ok so, here is the problem:

• This repository is built using father

• To generate optimal output, Babel needs to know which version of @babel/runtime you (in this case, @ant-design/pro-list) want to use. Why? For example, @babel/runtime/helpers/esm/regeberatorRuntime has been introduced in Babel 7.18.0, so Babel will inject an import to it only if "whoever called Babel" (father-build, in this case) told "Hey Babel, you can safely assume that I'm using @babel/runtime@^7.18.0".

• father-build uses require("@babel/runtime/package.json").version to detect the version: https://github.com/umijs/father/blob/master/packages/father-build/src/getBabelConfig.ts

• @and-design/pro-list depends on @babel/runtime@^7.16.3:

  pro-components/packages/list/package.json

  Line 39 in 4a4cc93

  "@babel/runtime": "^7.16.3",

• I believe that, when they published the last version of @and-design/pro-components, the maintainers of this package had @babel/runtime@7.18.0 in their node_modules and thus father assumed that ^7.18.0 was safe: for this reason, Babel injected that import/require to @babel/runtime/helpers/esm/regeneratorRuntime which was introduced in 7.18.0.

• I believe that your @ant-design/pro-list/node_modules/@babel/runtime is an older version, between 7.16.3 and 7.17.9 and thus @babel/runtime/helpers/esm/regeneratorRuntime does not exist.

How can this problem be fixed? (Note: these are 3 different solutions, sorted from the most ugly one to the best one)

1. You can make sure that @ant-design/pro-list/node_modules/@babel/runtime is at least 7.18.0. The safest way to do it is to add @babel/runtime@^7.18.0 as a dependency of your project, run yarn and then yarn dedupe (or npx yarn-deduplicate if you are using Yarn 1).
2. The maintainers of @and-design/pro-list can update their package.json to explicitly depend on 7.18.0 and not ^7.16.3. Also, I suggest using ~ instead of ^ to specify its version to avoid automatic minor updates, so that father won't accidentally tell Babel that it's safe to use a new version containing new helpers.
3. The maintainers of father should improve their @babel/runtime version detection logic:
   • Instead of using require("@babel/runtime/package.json").version, they could resolve the app/library's package.json file and read the version from require("/path/to/app/or/library/package.json").dependencies["@babel/runtime"].
   • They could provide an option in .fatherrc.js to specify which @babel/runtime version you want to target.

[stantoxt]

@nicolo-ribaudo Thank you so much. That's cool. I have spent time understanding this and benefit a lot from your detailed explanation.

• I believe that your @ant-design/pro-list/node_modules/@babel/runtime is an older version, between 7.16.3 and 7.17.9 and thus @babel/runtime/helpers/esm/regeneratorRuntime does not exist.
  I tested it and the version is 7.17.9.

1. You can make sure that @ant-design/pro-list/node_modules/@babel/runtime is at least 7.18.0. The safest way to do it is to add @babel/runtime@^7.18.0 as a dependency of your project, run yarn and then yarn dedupe (or npx yarn-deduplicate if you are using Yarn 1).

yarn dedupe is deprecated, I used yarn install --flat,but the choice answers are too many to choose it cause much time to choose the answers. I deleted node_modules and use command yarn install --flat --ignore-engines --ignore-platform , but this cause some library package compatibility problem, i would test it again.

• The maintainers of @and-design/pro-list can update their package.json to explicitly depend on 7.18.0 and not ^7.16.3. Also, I suggest using ~ instead of ^ to specify its version to avoid automatic minor updates, so that father won't accidentally tell Babel that it's safe to use a new version containing new helpers.

• The maintainers of father should improve their @babel/runtime version detection logic:

  • Instead of using require("@babel/runtime/package.json").version, they could resolve the app/library's package.json file and read the version from require("/path/to/app/or/library/package.json").dependencies["@babel/runtime"].
  • They could provide an option in .fatherrc.js to specify which @babel/runtime version you want to target.

I think the two other solutions should be the key to this problem.

At the end, @nicolo-ribaudo thanks again.

[nicolo-ribaudo]

yarn dedupe is deprecated, I used yarn install --flat,but the choice answers are too many to choose it cause much time to choose the answers.

You could also try to manually delete every @babel/runtime from your lockfile and then run yarn install, it might successfully install only the latest version.

[stantoxt]

yarn dedupe is deprecated, I used yarn install --flat,but the choice answers are too many to choose it cause much time to choose the answers.

You could also try to manually delete every @babel/runtime from your lockfile and then run yarn install, it might successfully install only the latest version.

let me have a try