Don't worry, I just wanted to start coding the tests with eslint v9.
I know that you are more skilled than me on this ;)

@KristjanESPERANTO

to be honest I have no clue about eslint but with this PR we have

	"dependencies": {
		"eslint": "^9.11.1",
	},
	"devDependencies": {
		"@eslint/js": "^9.11.1",
	},

in package.json, the versions are the same and both npm packages refer to the same github repo.

Is this correct or would be the one under dependencies sufficient?

eslint is the real ESLint which we need in dependencies because we use it in the config check.

@eslint/js is a plugin for ESLint that we use for linting - so devDependecies is the right place for it.

So everything is fine in my eyes.

Thanks for the explanation, I checked for dependency updates and saw the same update for both ...

The developers seem to synchronize the version number of both. So we will be seeing this even more often in the future.

I understand the doubt 🙂 They should have found a better name for the plugin.

hm, I tested now without the @eslint/js (see this commit) and all tests were fine (?)

Yes, it works because the plugin is a dependency of ESLint.

https://github.com/eslint/eslint/blob/main/package.json#L104

Isn't it recommended to put direct dependencies into the package.json? We import the plugin in the ESLint config.