Use `get-tsconfig` to locate, read and parse `tsconfig.json`

[SukkaW]

https://www.npmjs.com/package/get-tsconfig

[vitonsky]

Trust becomes an issue in the first few seconds of meeting

Why we need in this change? Do you have any problems with tsconfig lookup/parsing

[SukkaW]

Why we need in this change? Do you have any problems with tsconfig lookup/parsing

I have one ESLint config and multiple tsconfig.json files for a repo setup. Currently, eslint-plugin-paths only supports one tsconfig.json/jsconfig.json.

What get-tsconfig basically does is to pick up a proper tsconfig.json/jsconfig.json given a JS/TS file path.

Also, it has built-in JSONC parsing, so we can drop comment-json.

[vitonsky]

@SukkaW could you describe a project structure that would cause a problems with eslint-plugin-paths.

Ideally would be create an example repo. That would be useful to better understand your use case and then confirm it works fine once proposed changes would be applied.

[SukkaW]

@SukkaW could you describe a project structure that would cause a problems with eslint-plugin-paths.

Ideally would be create an example repo. That would be useful to better understand your use case and then confirm it works fine once proposed changes would be applied.

Sure, lemme see if I could spin up a re-production for this.