Add support for raising if you set a tsconfig entry of target/module with the right setting in the root

[orta]

Fixes #43293

[andrewbranch]

This seems like a nice addition, but why limit it to target and module? Surely we have an array of all valid or common option names somewhere, right?

[orta]

Just wanted to do the least to avoid this wrath by using what is probably always gonna be set there:

Other tools are allowed to use the top-level keys here, and do, so there's some danger of compat problems if in the future we add a compiler setting with the same name as a tool's setting

[andrewbranch]

What if you detect all compilerOptions keys in the root, but only issue an error if there is no compilerOptions object present at all? That way, third party tools could add any root key they want, even ones that share names with compilerOptions keys, as long as the user also added "compilerOptions": {}.

[orta]

This idea is great, I'll switch it to that

[andrewbranch]

All suggestions are for lazy array allocation

[DanielRosenwasser]

Would be nice to just avoid the linter suppression.

[DanielRosenwasser]

You could write json.compilerOptions === undefined and avoid the linter suppression, right?

[andrewbranch]

There’s also a hasProperty util

[orta]

OK, I've had a few looks over this will merge it at end of day