New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@babel/core^7.13.10 eslint error: Cannot read property 'value' of null when @babel/types are duplicated in node_modules #12985
Comments
Hey @roojay520! 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." |
Can you share the complete stack trace? |
So I had this issue a while back and fixed it via #10904 But I updated again and it is back.
|
I tried creating a project with the files in #12985 (comment) but I cannot reproduce the error 😕 @ChrisWiles / @roojay520 Could you also share a repository which reproduces the bug? 🙏 |
@nicolo-ribaudo Also I am using NPM v6.14.11 to install |
@nicolo-ribaudo Sorry! Because I'm using it with webpack, doesn't have complete stack trace. After debug yesterday, I found it should be the problem with the template string. When I prepared the demo again today, the error seemed to disappear again. It's weird. |
This issue is likely due to duplicate and different versions of That said, you can solve this issue by removing your lock files and installing again, or maybe |
Thanks, removing lock file and reinstalling didn't work. I will try dedupe
if that doesn't work I will try to make a reproducible repo
…On Wed, Mar 10, 2021, 7:31 AM Huáng Jùnliàng ***@***.***> wrote:
This issue is likely due to duplicate and *different* versions of
@babel/types in node_modules, although we tried to maintain
compatibilities across different versions, it is quite hard for us to
reproduce such issue because of the exponential combination of @babel/*.
That said, you can solve this issue by removing your lock files and
installing again, *or* maybe npm dedupe. But without a reproducing repo
we can't dig this issue further down.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12985 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACIEOMPCY7PXSAJZGCSFQYDTC5RB5ANCNFSM4Y3ANKSQ>
.
|
Minimal repro at https://github.com/kwangure/babel-eslint-property-null-repro. Hope it helps. |
So I solved my issue. Seemed to be a babel conflict, I was using
|
@kwangure Thanks for the reproduction repo. I can reproduce this issue. However, if I remove |
@JLHwung I don't know if it helps, but I noticed in that repository we generate different |
Yeah those tokens are generated from https://github.com/babel/babel/blob/main/eslint/babel-eslint-parser/src/convert/convertTokens.js#L22 . I can not reproduce this error on Babel repo, likely because we are using |
@kwangure I think I have figured out what's going wrong here. Currently You can check whether
It should look like
I removed the |
Trying to solve babel/babel#12985
Just |
We were able to solve this by not only deduping but also updating all of the nested versions. I found some on
Then I removed the newly saved dep from |
Bug Report
Error
Input Code
Expected behavior
The text was updated successfully, but these errors were encountered: