[Bug]: Warning: React version specified in eslint-plugin-react-settings must be a valid semver version, or "detect"; got “^17”

[Redirts]

Is there an existing issue for this?

• I have searched the existing issues and my issue is unique
• My issue appears in the command-line and not only in the text editor

Description Overview

I am getting this Warning message:

Warning: React version specified in eslint-plugin-react-settings must be a valid semver version, or "detect"; got “^17”

I have a .eslintrc file with this setup:

"settings": {
"react": {
"version": "detect"
},

Expected Behavior

This plugin should be able to cope with carets which are part of the semver specification

eslint-plugin-react version

v7.37.2

eslint version

v8.57.0

node version

v20.10.0

[ljharb]

Technically no, ranges are not part of the semver specification, they're something npm invented (although, they should be, and there's an open PR on the spec to add them).

It's meant to target a specific version. is there a reason you can't use "detect"?

[Redirts]

I currently have "detect" on the .eslintc file. Are you referring to adding that tag somewhere else?

[ljharb]

No, that’s what i meant. If you have that setting, where does the ^17 come from?

[Redirts]

Well, from what I gather, the "detect" tag in .eslintc is making the plugin fetch the ^17 from my package.json (from the react dependency) and hence giving the warning.

My package.json has this in the dependencies:
...
"react": "^17",
....

[ljharb]

The way "detect" works is it pulls the version number directly from the react you have installed on disk, so package.json shouldn't be involved at all (except in that it informs what ends up on disk).

[Redirts]

If not from my package.json then I don't where else it would retrieve ^17 from:
If I do "npm list" I get, for React:

├── [email protected]

[ljharb]

Can you use eslint --print-config=path/to/some/file and see what it says under settings? it's possible a shared config or a nested .eslintrc file is setting it to ^17.

[Redirts]

[Redirts]

Is there any news on this @ljharb ? Thanks

[ljharb]

I still can't reproduce or figure this out. Are you sure the output you gave was from that eslint command and not directly from your config in vscode?

[Redirts]

[ljharb]

ok, so then the computed config is still not ^17, and we still don't know where that's coming from. can you run the same command, but pass the path to a file that normally generates this error?

[Redirts]

Not sure I follow. Currently, I can see this error popping up during the execution of our sonarqube scan

Not quite sure why it is throwing that error....

[ljharb]

Does it only happen via sonarqube, not with the eslint cli?