Trace: isModuleDeclaration has been deprecated, please migrate to isImportOrExportDeclaration.

[jackngo]

I'm currently getting the following stacktrace, when compiling a Gatsby+Typescript project:

Trace: `isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`.
    at isModuleDeclaration (/.../ui/node_modules/@babel/types/src/validators/generated/index.ts:5869:11)
    at PluginPass.call (/.../ui/node_modules/babel-plugin-lodash/lib/index.js:102:44)
    at call (/.../ui/node_modules/@babel/traverse/src/visitors.ts:261:21)
    at NodePath._call (/.../ui/node_modules/@babel/traverse/src/path/context.ts:34:20)
    at NodePath.call (/.../ui/node_modules/@babel/traverse/src/path/context.ts:19:17)
    at NodePath.visit (/.../ui/node_modules/@babel/traverse/src/path/context.ts:92:31)
    at TraversalContext.visitQueue (/.../ui/node_modules/@babel/traverse/src/context.ts:144:16)
    at TraversalContext.visitSingle (/.../ui/node_modules/@babel/traverse/src/context.ts:108:19)
    at TraversalContext.visit (/.../ui/node_modules/@babel/traverse/src/context.ts:176:19)
    at traverseNode (/.../ui/node_modules/@babel/traverse/src/traverse-node.ts:34:17)
    at traverse (/.../ui/node_modules/@babel/traverse/src/index.ts:71:15)
    at transformFile (/.../ui/node_modules/@babel/core/src/transformation/index.ts:119:13)
    at transformFile.next (<anonymous>)
    at run (/.../ui/node_modules/@babel/core/src/transformation/index.ts:47:12)
    at run.next (<anonymous>)
    at transform (/.../ui/node_modules/@babel/core/src/transform.ts:29:20)
    at transform.next (<anonymous>)
    at step (/.../ui/node_modules/gensync/index.js:261:32)
    at /.../ui/node_modules/gensync/index.js:273:13
    at async.call.result.err.err (/.../ui/node_modules/gensync/index.js:223:11)

I was hoping someone could help me, as I've googled this trace error, and nothing comes up.

What does it mean? How do I fix it?

Example error reproduction here:

git clone https://github.com/jackngo/avvy-test.git
cd avvy-test/my-gatsby-site
npm i
npm run build

[benomatis]

@jackngo I got the same error, but only if I run gatsby develop after gatsby clean, and the site actually builds fine, no issues at all. If I re-run gatsby develop (without running gatsby clean before), I don't see the error anymore.

[subaquatic-pierre]

I am definitely getting the same error, @benomatis it seems what you say is correct. After gatsby clean I get the error, thereafter no errors. This is fine for development, but seem to be getting this error on our build pipeline, there is no cache so gatstby build produces the "isModuleDeclaration" error each time.

[benomatis]

I guess the reason I don't see the error on build is because I build from my local machine, and I'm guessing it's using the local cache I used for development. But is it also breaking something for you in build? Does it not finish building?

[subaquatic-pierre]

It runs to completion and everything seems to work fine despite the errors. It does show the same error "isModuleDeclaration" many times though. It looks to be some issue with gatsby-plugin-sharp.

[benomatis]

Yeah, I experienced the same, it shows multiple times, but does not disrupt the functionality of the app, so I'm not really devoting much of my time to it... for now... still watching this thread, of course...

[subaquatic-pierre]

or maybe not with that plugin as @jackngo doesn't seem to using it. It does seem to happen at createPage phase of build

[nicolo-ribaudo]

Technically this is just a warning and it can be ignored.

If you make sure to use the latest version of @babel/types, it will:

• actually print it as a warning, instead of a log
• print it at most once
• have a much shorter stack trace to be less noisy

[JLHwung]

This issue is being fixed in lodash/babel-plugin-lodash#260.

[benomatis]

Adding the following to resolutions in package.json, suggested in related issue comment lodash/babel-plugin-lodash#259 (comment), has fixed it for me (I had to delete yarn.lock and run yarn install for it to work):

"babel-plugin-lodash/@babel/types": "^7.21.2"

Now I have a much nicer warning and only once as follows:

warn `isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`
    at isModuleDeclaration (path/to/project/node_modules/@babel/types/lib/validators/generated/index.js:3940:35)
    at PluginPass.Program (path/to/project/node_modules/babel-plugin-lodash/lib/index.js:102:44)

(yes, I know it's a temporary fix until lodash/babel-plugin-lodash#260 is merged)

[jackngo]

Confirmed, adding "@babel/types": "^7.21.2", to devDependencies greatly reduced the output.

Does anyone know what the warning is referring to, and how to remedy it?

warn `isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`
    at isModuleDeclaration (.../node_modules/@babel/types/lib/validators/generated/index.js:3940:35)
    at PluginPass.Program (.../node_modules/babel-plugin-lodash/lib/index.js:102:44)

[timbryandev]

Sorry I'm a bit late to the party. I've had the same issue and I found this PR that seems to reference the change: #15266 (comment) and it gives some migration steps in the PR itself.

I found that PR while Googling wildly to try and work out what the issue was and also found this from Babel: https://babeljs.io/docs/babel-types

It may not help you, but hopefully will help others who find themselves here in the future! :D

[timbryandev]

My current plan is to follow the steps from the "Migration guide (for plugin authors)" section and use https://www.npmjs.com/package/patch-package to make the changes permanent to the babel-plugin-lodash library in our project and resolve the depreciation message.

[timbryandev]

UPDATE: I just published the fix under a fork of the original if that's easier for you: https://www.npmjs.com/package/@timbryandev/babel-plugin-lodash

[ruoduan-hub]

me too + 1