[Bug]: Nuxt 2.X build failing due to 'Cannot read properties of null (reading 'scope')' error in @babel/traverse

[apoorv1410]

💻

• Would you like to work on a fix?

How are you using Babel?

babel-loader (webpack)

Input code

Can't add the code here. Error occurs with npm run build command

Configuration file name

No response

Configuration

No response

Current and expected behavior

Current error screenshots:

Environment

• Babel [v 7.20.7]
• Nuxt [v 2.15.8]

Possible solution

No response

Additional context

The build is filing with Cannot read properties of null (reading 'scope') in @babel/traverse package version 7.20.7

[babel-bot]

Hey @apoorv1410! 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.

[babel-bot]

Hi @apoorv1410! This issue is missing some important information we'll need to be able to reproduce this issue.

Please understand that we receive a high volume of issues, and there are only a limited number of volunteers that help maintain this project. The easier it is for us to decipher an issue with the info provided, the more likely it is that we'll be able to help.

Please make sure you have the following information documented in this ticket:

1. Your Babel configuration (typically from .babelrc or babel.config.js)
2. The current (incorrect) behavior you're seeing
3. The behavior you expect
4. A short, self-contained example

Please provide either a link to the problem via the repl, or if the repl is insufficient, a new and minimal repository with instructions on how to build/replicate the issue.

[apoorv1410]

Fixed with updating node version from 16.13.1 to 16.14.2. Closing the issue now

[liuxingbaoyu]

It's weird and weirdly solved by upgrading nodejs, but glad it's working now.
If anyone else encounters this problem please reopen a reproducible issue.

[apoorv1410]

Update: just updating the nodejs version was not enough. We also had to downgrade to 7.20.5 explicitly from package.json with this code:

    "overrides": {
        "@babel/core": {
           ".": "7.20.5",
            "@babel/traverse":"7.20.5"
        }
    }

[xdlrt]

same issue at @babel/traverse, is there any progress?

[liuxingbaoyu]

Can anyone provide a repo that reproduces it?

[retyui]

@liuxingbaoyu sure:

• https://github.com/retyui/babel-issues-15299#readme

[liuxingbaoyu]

v7.20.10 is released, hoping to fix this issue.
https://www.npmjs.com/package/@babel/traverse

[necatisarhanli]

@liuxingbaoyu fix is legit , thanks everyone :)