Running next lint doesn't create a .eslintrc.json file when using the app directory.

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home
    Binaries:
      Node: 18.16.0
      npm: N/A
      Yarn: N/A
      pnpm: 8.6.0
    Relevant packages:
      next: 13.4.5-canary.4
      eslint-config-next: 13.4.4
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

https://github.com/tyler-lutz/playground

To Reproduce

Create a new project using the app directory and delete the .eslintrc.json file then run next lint.

Describe the Bug

Running next lint while using the app folder and not the pages folder doesn't create the .eslintrc.json file

Expected Behavior

Running next lint should create an .eslintrc.json file if one doesn't exist when using the app folder.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[danivideda]

I have this exact problem too.
ESLint only works when I build a new Next app with ESLint checked. Otherwise, running npm run lint or yarn lint after the Next app is created (without ESLint pre-configured when creating) will only install the dependencies but not create a new .eslintrc.json file as it should be

[Freshu23]

Same here 💁

[ryantang333]

Current workaround for those who are strictly using the app router is to just add an empty pages folder, run yarn lint to get the eslintrc.json created, then delete the pages folder.

[Hoody91]

Confirmed this is still happening on Next 14.0.0, although the workaround @ryantang333 mentioned did work and created the eslintrc.json as expected

[derekjwilliams]

ryantang333 has the workaround, thanks so much. But I'm surprised that this is not better documented. I wasted a bit of time trying to figure this out. Should likely not be marked as Closed since the Next eslint plugin instructions don't include the workaround.

[Zenb0t]

Seems to be fixed here.

I was running version on "next": "14.1.0", and still had the issue. Workaround fixed it.

[devjiwonchoi]

Fixed by #50761. Thank you for opening the issue!

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.