include and exclude have no effect

[GreenDjango]

Hi,

tsconfig.json files specified using extends will have include and exclude paths relative to their location, as per the include docs:

These filenames are resolved relative to the directory containing the tsconfig.json file.

So a config like Next.js base install with npm will produce a typescript error:

error TS18003: No inputs were found in config file '/home/user/my-project/tsconfig.json'.
Specified 'include' paths were '["node_modules/@tsconfig/next/next-env.d.ts","node_modules/@tsconfig/next/**/*.ts",...]'
and 'exclude' paths were '["node_modules/@tsconfig/next/node_modules"]'.

for a tsconfig.json like:

{
  "extends": ["@tsconfig/next/tsconfig.json"],
}

Not specify include and exclude in base template can remove ambiguity

Have a nice day

[zetaraku]

Agreed. include and exclude in the @tsconfig/next/tsconfig.json file are useless and misleading.

Maybe we can remove that and provide this excerpt in the README file and instruct users to manually add it:

{
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", ".next/types/**/*.ts"],
  "exclude": ["node_modules"]
}

[joshunger]

Wouldn't using ${configDir} in include work in base?

[vladshcherbin]

The main readme file is misleading and the example code it has is not working due to this behavior.

[orta]

You are welcome to add notices to the configs when it makes sense, like we did with baseUrl in #248

[vladshcherbin]

@orta the whole next config file is outdated and gives errors even by next cli itself

I can update the docs and the configuration to latest version which next team actually uses and provides in new projects since next 15 if you accept a major version bump

I also found previous attempts of similar changes in #232 and #243 but none of them landed. Just asking before making changes if you are okay with them

[orta]

Strange, I accepted one, unsure why it didn't land. Seems fine with me