-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
You gave us a visitor for the node type ClassAccessorProperty but it's not a valid type #15765
Comments
Hey @nagasundram! 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 attach the output of |
|
Please attach the whole input, they are important. The |
Can you please share the older version which does not support ClassAccessorProperty @JLHwung? |
We are still triaging this issue. If it comes from an official Babel plugin, it will be fixed. If you want to prioritize this issue, please provide a reproduction repo. |
@JLHwung this issues is happening only after auto upgrade of @babel/traverse 7.22.8. (dependency package of some libraires) so if we downgrade the @babel/traverse version will it solve this issue. |
@JLHwung Please refer one of the repo affected because of this error
|
The |
@JLHwung Any possible fix version can we expect? |
Can you share the lock file? Unfortunately without the reproduction dependency maps, we can not know what is going wrong here. |
I have the same issue, I deleted my package -lock.js and my node modules, it happens the same error, I'm actually update my babel/types to 7.17.0 , but it doesn't work, it seems what napat-u said was correct, but I don't find how to solve it. Some one ,has any idea? |
@Cessilva please provide a reproduction repo if you want this issue to be prioritized. Unfortunately it is very hard to reproduce compatibility issues like that without such repo, otherwise it would have been caught by our CI. |
@JLHwung https://github.com/knownasilya/ember-toggle/tree/v7.1.1 please check this package at v7.1.1 |
@nagasundram Can you print the top level
|
@nagasundram @Cessilva I have posted some speculation about this issue on #15771 as I can't confirm because we don't have a reproduction repo. Let me know if that is exactly the case. You can fix this issue without waiting for a patch. |
We are also facing similar issue
Is there any solution? |
I also have this problem on my side, and the gitlab-cli build has been failing since today. The local pnpm version was found to be inconsistent with the pnpm version of the builder. The pnpm version of the builder was upgraded to resolve the problem |
If anyone can share a repository that shows the error, that would be really helpful for us to be sure about what's going on. |
for us This was an issue
|
Same error here since few days.
|
Exactly Same issue am facing while running 'yarn start' It was working with node version 14, but when we upgraded node version to 18.15.0 , it started throwing error. Any help or pointers would be appreciated |
I am facing the same issue but with capacitor Error: /opt/build/repo/node_modules/@capacitor/app/dist/esm/web.js: You gave us a visitor for the node type ClassAccessorProperty but it's not a valid type Any help would be appreciated. |
Same error here
|
Can someone share a repository please? 🙏 |
I can't share the repository but i can share the result of npm ls @babel/types :
|
I'm encountering the same problem. |
For those affected by this issue, please upgrade to Babel 7.22.9:
|
Upgrading to Babel 7.22.9 solved my problem. |
Thanks @JLHwung for all your effort Unfortunately, it didn't help , post upgrading the @babel/core to 7.22.9 and running yarn dedupe, Still getting the same error. |
@JLHwung Thanks for getting onto this so quickly. Because mine was in a dependency I did not have to update any babel packages myself. Instead I ran npm install and then npm dedupe and then I was able to successfully build my application 👍 |
We solved by doing this:
And my babel/core version was:
DON'T forget doing:
|
thank you guys for your efforts but upgrading to babel 7.22.9 still doesn't fix the issue on our side |
@aatishbarnwal @7orry Can you share the output of |
@nicolo-ribaudo here is the output of
and this after the update to latest version
|
Thank you! Do you also have the error stack trace? The underlying problem is mixing different versions of I think we could relax the error and make it a warning instead, to avoid this problem in the future, but we cannot retroactively change |
thank you @nicolo-ribaudo, i think we don't have much informations on the stack trace
i tried to override the |
Oh, you are on a version of I think the only solution is to make sure that your unbundled version of
It will fix the error only once Next updates their bundled Babel version to the new version. |
@johnny-washswat , Thanks for your input, It worked for us , you made my day :).
And UI was up and running, Thanks @JLHwung for all your assistance over this, Really appreciate. |
@aatishbarnwal can you please share which next.js version you use and also the babel/* versions 🙏🏻 ? |
Hello again @nicolo-ribaudo, like @JLHwung mentioned that
and also added the resolution like you suggested
but sill have the same error message, am i doing the resolution wrong @nicolo-ribaudo ? |
any more help please on this, i'm still blocked 🙏🏻 |
You need an older version, that does not include ClassAccessorProperty in the supported features, so that it can work with the even older version bundled by Next.js (7.12.12) |
I tried version configuration a number of times, and this problem was also solved under the old version of next, which needed to be fixed by adding the following configuration to lock the dependent version "resolutions": { |
Try this code in your package.json, it effect for me. "overrides": { |
thanks a lot 🙏🏻 @nicolo-ribaudo for your help we finally fixed the issue by upgrading Next.js |
💻
How are you using Babel?
@babel/cli
Input code
...
Configuration file name
No response
Configuration
No response
Current and expected behavior
After upgrading to 7.22.8 this issue is coming
Environment
Possible solution
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: