We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This config uses a depracted key which causes the following issue:
Oops! Something went wrong! :(
ESLint: 9.8.0
A config object is using the "parserOptions" key, which is not supported in flat config system.
Flat config uses "languageOptions.parserOptions" to specify parser options.
Please see the following page for information on how to convert your config object into the correct format: https://eslint.org/docs/latest/use/configure/migration-guide#configuring-language-options
If you're not using "parserOptions" directly (it may be coming from a plugin), please see the following: https://eslint.org/docs/latest/use/configure/migration-guide#using-eslintrc-configs-in-flat-config ELIFECYCLE Command failed with exit code 2.
The text was updated successfully, but these errors were encountered:
We don't support flat config yet; see #993.
Sorry, something went wrong.
No branches or pull requests
This config uses a depracted key which causes the following issue:
Oops! Something went wrong! :(
ESLint: 9.8.0
A config object is using the "parserOptions" key, which is not supported in flat config system.
Flat config uses "languageOptions.parserOptions" to specify parser options.
Please see the following page for information on how to convert your config object into the correct format:
https://eslint.org/docs/latest/use/configure/migration-guide#configuring-language-options
If you're not using "parserOptions" directly (it may be coming from a plugin), please see the following:
https://eslint.org/docs/latest/use/configure/migration-guide#using-eslintrc-configs-in-flat-config
ELIFECYCLE Command failed with exit code 2.
The text was updated successfully, but these errors were encountered: