-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore: there were JSX issues #13
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm pretty critical about whether all this configuration overhead is going to give us the benefit we're looking for.
But that's where I trust you guys, as you have a lot more experience with the whole JS ecosystem.
So LGTM from my side.
What would be another option? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good with the exclude
I also removed the node types are they're no longer needed with the exclude defined. |
Fixes issues with JSX and node type import