Fixes #31: Problem when using a custom configFile name

src/tsconfig-loader.ts

@@ -73,6 +73,10 @@ export function resolveConfigPath(
     return absolutePath;
   }
 
+  if (fs.statSync(cwd).isFile()) {
+    return path.resolve(cwd);
+  }
+
   const configAbsolutePath = walkForTsConfig(cwd);
   return configAbsolutePath ? path.resolve(configAbsolutePath) : undefined;
 }

test/config-loader-tests.ts

@@ -1,6 +1,7 @@
 import { assert } from "chai";
 import {
   configLoader,
+  loadConfig,
   ConfigLoaderFailResult,
   ConfigLoaderSuccessResult
 } from "../src/config-loader";
@@ -73,4 +74,17 @@ describe("config-loader", (): void => {
     assert.equal(failResult.resultType, "failed");
     assert.isTrue(failResult.message.indexOf("baseUrl") > -1);
   });
+
+  it("should presume cwd to be a tsconfig file when loadConfig is called with absolute path to tsconfig.json", () => {
+    // using tsconfig-named.json to ensure that future changes to fix
+    // https://github.com/dividab/tsconfig-paths/issues/31
+    // do not pass this test case just because of a directory walk looking
+    // for tsconfig.json
+    const configFile = join(__dirname, "tsconfig-named.json");
+    const result = loadConfig(configFile);
+
+    const successResult = result as ConfigLoaderSuccessResult;
+    assert.equal(successResult.resultType, "success");
+    assert.equal(successResult.configFileAbsolutePath, configFile);
+  });
 });

test/tsconfig-named.json

@@ -0,0 +1,10 @@
+{
+  "extends": "../base-tsconfig.json",
+  "compilerOptions": {
+    "baseUrl": ".",
+    "module": "commonjs",
+    "target": "es6",
+    "sourceMap": true,
+    "outDir": "./js_out"
+  }
+}