fix: don't ignore the tsconfig file name in project paths or path pat…

…terns

`getTsConfig` treats every path as a directory and looks for a `tsconfig.json` in the closest parent directory

this breaks any configuration that uses file names other than tsconfig.json, as is convention for [solution-style](https://devblogs.microsoft.com/typescript/announcing-typescript-3-9/#solution-style-tsconfig) tsconfigs, which is exacerbated by the lack of support for the `references` field (see import-js#94)

src/index.ts

@@ -9,7 +9,7 @@ import {
   Resolver,
   ResolverFactory,
 } from 'enhanced-resolve'
-import { createPathsMatcher, getTsconfig } from 'get-tsconfig'
+import { createPathsMatcher, getTsconfig, parseTsconfig } from 'get-tsconfig'
 import isCore from 'is-core-module'
 import isGlob from 'is-glob'
 import { createSyncFn } from 'synckit'
@@ -350,7 +350,10 @@ function initMappers(options: TsResolverOptions) {
   ]
 
   mappers = projectPaths.map(projectPath => {
-    const tsconfigResult = getTsconfig(projectPath)
+    const tsconfigResult =
+      fs.existsSync(projectPath) && fs.statSync(projectPath).isFile()
+        ? { path: projectPath, config: parseTsconfig(projectPath) }
+        : getTsconfig(projectPath)
     return tsconfigResult && createPathsMatcher(tsconfigResult)
   })