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

Eslint warning in the starting repository generated by the with-typescript-eslint-jest example #21162

Closed
kaznak opened this issue Jan 15, 2021 · 1 comment · Fixed by #21163
Closed
Labels
examples Issue/PR related to examples good first issue Easy to fix issues, good for newcomers

Comments

@kaznak
Copy link
Contributor

kaznak commented Jan 15, 2021

What version of Next.js are you using?

10.0.5

What version of Node.js are you using?

14.15.1

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

next start

Describe the Bug

When I use the example, with-typescript-eslint-jest example, I always met following warning in the default file tree:

 % yarn lint
yarn run v1.22.10
$ eslint . --ext ts --ext tsx --ext js
Warning: React version not specified in eslint-plugin-react settings. See https://github.com/yannickcr/eslint-plugin-react#configuration .
✨  Done in 2.26s.

I want to suppress this message.

Expected Behavior

The lint message should be the following:

 % yarn lint
yarn run v1.22.10
$ eslint . --ext ts --ext tsx --ext js
✨  Done in 2.17s.

To Reproduce

Execute following commands

npx create-next-app --example with-typescript-eslint-jest test
cd test
yarn lint

Thank you for reading!

@kaznak kaznak added the bug Issue was opened via the bug report template. label Jan 15, 2021
@timneutkens timneutkens added good first issue Easy to fix issues, good for newcomers examples Issue/PR related to examples and removed bug Issue was opened via the bug report template. labels Jan 15, 2021
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
examples Issue/PR related to examples good first issue Easy to fix issues, good for newcomers
Projects
None yet
3 participants