typescript-config/is-valid does not recognize Node.js `extends` paths

[Etienne Dechamps]

🐞 Bug report

The TSConfig extends option explicitly supports Node.js style resolution, meaning it is possible to write:

{
    "extends": "@tsconfig/strictest/tsconfig.json"
}

This works perfectly fine as far as the TypeScript compiler is concerned, but webhint 6.2.0 doesn't seem to recognize the path:

typescript-config/is-valid: 1 hints
hint #1: ENOENT: no such file or directory, open '/myproject/@tsconfig/strictest/tsconfig.json'

Normal filesystem paths, e.g. node_modules/@tsconfig/strictest/tsconfig.json, work fine.

[Tony Ross]

Thanks for the report @dechamps! Definitely something we should fix.