Skip to content
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

[v4] Bug: "React must be in scope" should not fire when using new JSX transform #19992

Closed
gaearon opened this issue Oct 9, 2020 · 3 comments
Closed
Labels
Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug

Comments

@gaearon
Copy link
Collaborator

gaearon commented Oct 9, 2020

If you use new JSX transform (e.g. with 17 RC3), you still can't remove the React import because of the ESLint rule. We should automatically disable that rule when we use the new JSX transform.

@gaearon gaearon added the Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug label Oct 9, 2020
@Maskedman99
Copy link

Maskedman99 commented Oct 15, 2020

Same issue in v16.4.0

@Maskedman99
Copy link

@gaearon
Copy link
Collaborator Author

gaearon commented Oct 16, 2020

Lool I meant to file this in CRA repo.

@gaearon gaearon closed this as completed Oct 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug
Projects
None yet
Development

No branches or pull requests

2 participants