We probably can't do this, not all projects have "src" as their default folder I think

I think removing the src from react example, and keeping the README the same is probably the right call

well, reverted that changes. :)

Thanks! It will deploy overnight

I ran into this problem today - 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.

One way to get around it is to specify relative paths:

  "include": [
    "../../../../**/.eslintrc.cjs",
    "../../../../next-env.d.ts",
    "../../../../**/*.ts",
    "../../../../**/*.tsx",
    "../../../../**/*.js",
    "../../../../**/*.jsx",
    "../../../../**/*.cjs",
    "../../../../**/*.mjs"
  ],

But then you're encoding your node_modules directory structure into the config as well... 🤔

Hm... would be great to get a <root> capability to add to include and exclude paths to refer to the directory with the package.json file, like Jest's <rootDir> option:

  "include": [
    "<root>/**/*.ts"
  ]

@orta I guess this doesn't exist in TS, right?

Edit: opened a feature request in the TypeScript repo here: microsoft/TypeScript#51213