Yarn lint causes error: The "path" argument must be of type string. Received undefined

[emadabdulrahim]

What version of Next.js are you using?

11.1.0

What version of Node.js are you using?

v15.2.1

What browser are you using?

Chrome

What operating system are you using?

macOSv11.4

How are you deploying your application?

Custom deployment

Describe the Bug

I upgraded from next@10.2 to next@11.1.0. Then I followed the guide for extending @next/eslint-plugin-next my project already has .eslintrc setup.

Here's my .eslintrc

"extends": ["airbnb-typescript-prettier", "plugin:@next/next/recommended"],

my next.config.js

reactStrictMode: true,
  webpack(config) {
    config.module.rules.push({
      test: /\.svg$/,
      use: ['@svgr/webpack'],
    })

    return config
  },
  distDir: **'build',

The bug

when I run yarn lint I get this error

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Not sure what's causing it. Any idea?

Expected Behavior

Should be able to run yarn lint without errors

To Reproduce

I'm not sure how to reproduce in a different repo.

[stefanprobst]

i think this is caused by

next.js/packages/next/lib/eslint/runLintCheck.ts

Line 201 in 40f85f6

path.dirname(deps.resolved.get('eslint-config-next')!),

could you try if you still get the error after yarn add -D eslint-config-next?

[AriPerkkio]

This is likely same as #28030. I wasn't able to find this issue with search by using no-html-link-for-pages as keyword.

There's easy repro in that other issue so I'll leave it open instead of closing as duplicate.

[emadabdulrahim]

Hi @stefanprobst. I tried your suggestion and it worked. Thanks!

Installing eslint-config-next solved the issue. Closing.

[stefanprobst]

@emadabdulrahim cool, thanks for checking! - i still think it should work without having to install eslint-config-next - so let's keep this issue open?

@AriPerkkio looks like this is actually a different issue

[stefanprobst]

@housseindjirdeh could you clarify if eslint-config-next always needs to be installed for next lint to work, even when it is not used in the eslint config? thanks!

[Axedyson]

Yeah I think eslint-config-next shouldn't be required to make this work as well

[bryanmig]

I'm using pnpm and experienced this as well. This issue only appeared when plugin:@next/next/recommended was added to my extends array but installing eslint-config-next did fix it for me.

[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.