-
Notifications
You must be signed in to change notification settings - Fork 74
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
TypeError: Cannot read properties of undefined (reading 'columnNumber') #71
Comments
I ran into the same issue while trying to use this with nextjs 13. So one way to make this work with nextjs 13 may be to use babel instead of swc by creating a .babelrc file at the root of the project. (I could not try this myself because I need swc). Another possible way could be to generate the |
Also having this issue, but we aren't using Babel nor SWC, as the other comment indicated. We use only |
Please prioritise this issue. It has a severe impact on workflow. P.S. I'm using Next.j 14.0.3 and the new App Router. |
The issue was introduced by the babel plugin transform react jsx source in v7.9.0 Since newer plugin versions dont support retrieving a column number anmyore, 0 should be used as a fallback imo. The column number isnt that important, since we only look for whole components anyway. https://babeljs.io/docs/babel-plugin-transform-react-jsx-source |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Next.js v13.1.6-canary.3
react 18
The text was updated successfully, but these errors were encountered: