yarn lint not working on brand new app

[vixalien]

What version of Next.js are you using?

11.1.2

What version of Node.js are you using?

16.6.1

What browser are you using?

Edge 94

What operating system are you using?

Windows 11 (Insider build: 22000.258)

How are you deploying your application?

next start

Describe the Bug

When I create a brand new app using yarn create next-app, and try to run yarn lint, an error is thrown:

I wanted to try out linting cause apparently Im a bad developer for not doing so and I don't know what I'm doing wrong.

Expected Behavior

I would have expected it to lint my app

To Reproduce

1. Create a brand new app using yarn create next-app
2. Run next lint in the app directory

[chongruei]

I've just downgrade Eslint from 8.0.1 to 7.32.0 then it's work.

[vixalien]

I've just downgrade Eslint from 8.0.1 to 7.32.0 then it's work.

I will try that when I get access to the terminal but I think that this is a bug somehow

[wjd3]

This is definitely related to eslint version 8.0.1. I started getting this error right after upgrading major versions.

[gaston-flores]

I think this is related to a change in eslint's package.json. They added this field:

  "exports": {
    "./package.json": "./package.json",
    ".": "./lib/api.js",
    "./use-at-your-own-risk": "./lib/unsupported-api.js"
  },

Which causes the require in hasNecessaryDependencies to throw this error:

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/api.js' is not defined by "exports" in C:\Users\user\Repos\eslint-bug-test\node_modules\eslint\package.json

Removing the exports field manually from eslint's package.json also fixes this issue.

[stefanprobst]

see #29770 (comment)

[housseindjirdeh]

Closing as this is a duplicate. Like others mentioned, you'll need to downgrade to v7 for the meantime.

There's an open PR to add support for v8 (#29865). Once all sub-dependencies used in Next.js' ESLint config and plugin is supported, it'll be merged!

[balazsorban44]

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.