test: add case for resolving paths from an extended tsconfig (#166)

Co-authored-by: Alec Larson <1925840+aleclarson@users.noreply.github.com>

Author: jdharrisnz

test/__fixtures__/extends-paths/case.md

@@ -0,0 +1 @@
+The focal point of this case is to ensure that the `paths` are resolved correctly when a project extends another project that has `paths` defined in its `compilerOptions`.

test/__fixtures__/extends-paths/config.json

@@ -0,0 +1,3 @@
+{
+  "root": "./my-app"
+}

test/__fixtures__/extends-paths/my-app/index.ts

@@ -0,0 +1,3 @@
+import { message } from '@/message'
+
+console.log(message)

test/__fixtures__/extends-paths/my-app/message.ts

@@ -0,0 +1 @@
+export const message = 'Hello world'

test/__fixtures__/extends-paths/my-app/tsconfig.json

@@ -0,0 +1,4 @@
+{
+  "extends": "../tsconfig.json",
+  "include": ["./"]
+}

test/__fixtures__/extends-paths/tsconfig.json

@@ -0,0 +1,12 @@
+{
+  "compilerOptions": {
+    "module": "esnext",
+    "moduleResolution": "bundler",
+    "skipLibCheck": true,
+    "paths": {
+      "@/*": ["./my-app/*"]
+    }
+  },
+  "include": [],
+  "references": [{ "path": "./my-app/" }]
+}