[Bug]: isModuleDeclaration has been deprecated, please migrate to isImportOrExportDeclaration

[kiran-chauhan-rapidops]

💻

• Would you like to work on a fix?

How are you using Babel?

Other (Next.js, Gatsby, vue-cli, ...)

Input code

Stack trace

`isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`
  at isModuleDeclaration (/home/project/node_modules/@babel/types/lib/validators/generated/index.js:3940:35)
  at NodePath.<computed> [as isModuleDeclaration] (/home/project/node_modules/@babel/traverse/lib/path/index.js:241:12)
  at PluginPass.addHelper (/home/project/node_modules/@babel/core/lib/transformation/plugin-pass.js:36:22)
  ...
  ...
  ...
  at buildCreateElementOpeningElementAttributes (/home/project/node_modules/@babel/plugin-transform-react-jsx/lib/create-plugin.js:507:144)
  at buildCreateElementCall (/home/project/node_modules/@babel/plugin-transform-react-jsx/lib/create-plugin.js:446:64)
  at PluginPass.exit (/home/project/node_modules/@babel/plugin-transform-react-jsx/lib/create-plugin.js:189:26)

Configuration file name

No response

Configuration

No response

Current and expected behavior

This warning should not come.

Environment

• Node: 16.16.0
• npm: 8.11.0
• eslint: 8.14.0

Possible solution

No response

Additional context

This error is coming in one of the existing React project created using create-react-app. Following is the chain of the packages depends on -

eslint-config-react-app > babel-preset-react-app > @babel/preset-react > @babel/plugin-transform-react-jsx > @babel/types

[babel-bot]

Hey @kiran-chauhan-rapidops! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite.

[nicolo-ribaudo]

Could you share your lockfile, to know the versions of the various Babel packages?

[nicolo-ribaudo]

Also, make sure that you have at least version 7.20.7 of @babel/traverse and @babel/helpers, when we removed usage of the deprecated function. If they are older, delete these two packages from your package-lock.json/yarn.lock/pnpm-lock.yaml file and re-install your deps.

[zeroimpl]

I just had same issue after installing @babel/preset-typescript to an existing project, but then doing npm update resolved it.

[liuxingbaoyu]

#15484 should fixed this.

[benomatis]

I still see the warning on core v7.21.8 where the changes in #15484 are supposed to be...

"@babel/core": "^7.21.8",
"@babel/eslint-parser": "^7.21.8",
"@babel/preset-react": "^7.18.6",

[nicolo-ribaudo]

The warning still appears in case third party code (i.e. not code controlled by us, either now or in the past) uses the deprecated API.