Errorneous linting of jsx fragments

[vadzim]

Is this a bug report?

yes

Steps to Reproduce

1. create app npx create-react-app app
2. replace content of src/App.js with

import React from 'react';

const App = (
  <>App</>
);

export default App;

3. run npx eslint ./src inside app

Expected Behavior

no errors, no warnings

Actual Behavior

There is a warning:

.../src/App.js
  1:8  warning  'React' is defined but never used  no-unused-vars

✖ 1 problem (0 errors, 1 warning)

If I remove react import from src/App.js, then it shows an error:

.../src/App.js
  2:3  error  'React' must be in scope when using JSX  react/react-in-jsx-scope

✖ 1 problem (1 error, 0 warnings)

Reproducible Demo

https://github.com/vadzim/errorneous-fragment-linting.git

[bugzpodder]

[edit] Oops, I missed your package.json which extends react-app

[yordis]

Wouldn't be the case that this is happening because CRA does not use .eslintrc or any other file that eslint command would use instead it is passing the config directly in the loader

create-react-app/packages/react-scripts/config/webpack.config.dev.js

Line 192 in 05d3fd2

extends: [require.resolve('eslint-config-react-app')],

[vadzim]

It seems this is fixed in jsx-eslint/eslint-plugin-react@18898e1#diff-d41ba36daf851354b9587064dc4ee0ac
but still not published

[stale]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

[tim-phillips]

Issue tracking the publication of a new release: jsx-eslint/eslint-plugin-react#2046

[stale]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.

[stale]

This issue has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue.