Loosest/least-strict/most laxed config option

[devinrhode2]

opposite of strictest

Could be discovered here: https://stackoverflow.com/questions/59506821/starter-tsconfig-json-that-is-the-most-laxed-loose-for-pure-javascript-projects

[orta]

Interesting, in many ways an empty tsconfig.json / jsonconfig.json is sort of the lower bounds for the strictness of a project. Which makes shipping a lax mode basically a NOOP I think.

Under the hood .ts files get the 'full' type checker, and .js files get a lot of simplifications - there's not really a way to make a .ts file get those .js files' laxness via a tsconfig entry

[devinrhode2]

Another way to arrive at a similar answer:

1. Reverse everything in the strictest config
2. Remove rules which are simply asserting defaults

However, there are a few rules which, if undefined, still provide you ide hints, but don't register on any sort of tsc cli command.

So for those few properties, if we want to maximally reduce cognitive burden, those rules should be explicitly disabled.