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

Setting up a linter isn't work since ^9.0.0 #1568

Open
thiendaovotran opened this issue Jul 10, 2024 · 1 comment · May be fixed by #1557
Open

Setting up a linter isn't work since ^9.0.0 #1568

thiendaovotran opened this issue Jul 10, 2024 · 1 comment · May be fixed by #1557

Comments

@thiendaovotran
Copy link

thiendaovotran commented Jul 10, 2024

Describe the bug

Following up the guide I have discovered that from version 9, there are few change in ESLint which will require to migration from .eslintrc.json to eslint.config.js.
Downgrade to version 8 (^.8.56.0) seem to be fine or perform migration on your own following the guide. But I think we should have the update on this.

Oops! Something went wrong! :(

ESLint: 9.6.0

ESLint couldn't find an eslint.config.(js|mjs|cjs) file.

From ESLint v9.0.0, the default configuration file is now eslint.config.js.
If you are using a .eslintrc.* file, please follow the migration guide
to update your configuration file to the new format:

https://eslint.org/docs/latest/use/configure/migration-guide

If you still have problems after following the migration guide, please stop by
https://eslint.org/chat/help to chat with the team.

To Reproduce

  1. Go to Guide
  2. Following up the guide until section Setting up a linter
  3. Try to run npx eslint . for example
  4. Got the error

Screenshots

No response

Device (please complete the following information)

  • Eslint ^9.6.0
  • Discord.js Guide v14 | Setting up a linter

Additional notes

No response

@imnaiyar
Copy link
Contributor

There's already a pr for this #1557

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants