despite parserOptions.project: './tsconfig.eslint.json' explicitly having include: ["**/*.js"]

It doesn't have allowJs or checkJs though. So I think TS ignores the JS files from the glob.

...which brings up the question, why was this passing in v7? What changed?

v7.18.0...v8.0.1

IDK we can poke and see what might have caused it

we enabled single run inference by default -- maybe that changed their lint run?

I also have a similar issue here
The difference is that the errored files are explicitly listed in my tsconfig

I AM NOT THE ONLY ONE! THIS WAS DRIVING ME BANANAS!

I have this problem using both the classic project and new fancy projectService config opts

I am experiencing it with (PROJROOT)/*.config.ts files. the files are 100% in my tsconfig. The problem goes away if I take the EXACT same config and rename it to tsconfig.json, but if I use tsconfig.lint.json/tsconfig.eslint.json (with the same exact eslint settings except for the project/tsconfig path) I get 0:0 error Parsing error: ~/projthingy/yet-another-stupid-config-file.config.ts was not found by the project service. Consider either including it in the tsconfig.json or including it in allowDefaultProject

The problem goes away if I take the EXACT same config and rename it to tsconfig.json

Aha! For parserOptions.projectService, there's your issue. When we say "the same logic as your editor", we mean it only picks up tsconfig.json files. This is something we should put in the FAQs (linking: #9753). Quite a few folks are getting tripped up by it; I don't think this is clear enough in the docs.

Btw, for the project service, the only way to load in a file other than that is the allowDefaultProject & defaultProject options. Those only apply for "out-of-project" files (those not in a tsconfig.json). These are the things mentioned later down in https://typescript-eslint.io/blog/announcing-typescript-eslint-v8#project-service.

@JoshuaKGoldberg Aha back at ya! That does make sense (despite being super tired — dog was bruffing all night at the neighborhood).

What if I want do not include stuff in my tsconfig.json and it is my primary “build” config? I have a million “tsconfig.eslint.json” files and flip flopping my build setups around sounds annoying. Does projectService grep around for adjacent tsconfig looking things?

Then your best bet is to stick with parserOptions.project. Which is another good FAQ to note for #9753. If you're using tsconfig.jsons for building in a way that conflicts with intellisense then parserOptions.project will give you the fine-grained control you're looking for.

Anyway, this specific issue was meant to be for parserOptions.project in the first place, so I'd say if you have more issues there it'd be good to file a new issue or discussion.

Sounds good to me! Thanks for your speedy responses. I guess moving to using “tsconfig.build.json” isn’t a terrible thing.

Ok! Added a note to #9753 (comment) that this is an FAQ. Thanks all!