next lint adds unnecessary absolute path distDir to include in tsconfig.json

[devjiwonchoi]

Link to the code that reproduces this issue

https://github.com/devjiwonchoi/repro-next-lint-adds-unnecessary-tsconfig-include

To Reproduce

1. Run pnpm next lint
2. It will modify the tsconfig.json to add an unnecessary include.

Current vs. Expected behavior

Adds absolute path to the distDir, which is a duplicate of ".next/types/**/*.ts".

{
  "compilerOptions": {
    "include": [
      "next-env.d.ts",
      "**/*.ts",
      "**/*.tsx",
      ".next/types/**/*.ts",
      "/Users/devjiwonchoi/DevLife/OpenSource/jiwonchoi.dev/.next/types/**/*.ts"
    ],
  }
}

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.1.0: Mon Oct  9 21:32:11 PDT 2023; root:xnu-10002.41.9~7/RELEASE_ARM64_T6030
  Available memory (MB): 18432
  Available CPU cores: 11
Binaries:
  Node: 18.17.1
  npm: 9.6.7
  Yarn: 1.22.19
  pnpm: 8.15.4
Relevant Packages:
  next: 14.1.2-canary.3 // Latest available version is detected (14.1.2-canary.3).
  eslint-config-next: 14.1.2-canary.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

ESLint (eslint-config-next)

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

This issue was introduced on the latest canary version. Suspecting #61877.

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