feat: TypeScript + VS Code improvements (#33)

These are small changes to fix issues noticed while working from this
template on https://github.com/valora-inc/identity-service

- Only use relative imports for now: see
valora-inc/identity-service#29
- VS Code:
- workaround to avoid seeing incorrect errors when working in
`*.test.ts` files
- use TypeScript version from the project instead of the one bundled in
VS Code to avoid seeing incorrect TS issues

.eslintrc.js

@@ -1,7 +1,7 @@
 module.exports = {
   extends: ['@valora/eslint-config-typescript'],
   parserOptions: {
-    project: './tsconfig.eslint.json',
+    project: './tsconfig.test.json',
   },
   rules: {
     // Maybe move it to @valora/eslint-config-typescript?

.vscode/settings.json

@@ -0,0 +1,4 @@
+{
+  // Use the project's TypeScript version instead of the one bundled with VS Code
+  "typescript.tsdk": "node_modules/typescript/lib"
+}

jest.config.js

@@ -5,7 +5,7 @@ module.exports = {
   // Allow absolute imports from the tsconfig baseUrl
   moduleDirectories: ['node_modules', '<rootDir>'],
   transform: {
-    '^.+\\.(ts|tsx)$': 'ts-jest',
+    '^.+\\.(ts|tsx)$': ['ts-jest', { tsconfig: 'tsconfig.test.json' }],
   },
   testPathIgnorePatterns: ['dist'],
   setupFiles: ['<rootDir>/jest.setup.js'],

src/index.test.ts

@@ -1,4 +1,4 @@
-import { main } from 'src'
+import { main } from './index'
 
 describe(main, () => {
   it("should return 'Hello, world!'", () => {

src/tsconfig.json

@@ -0,0 +1,6 @@
+{
+  // Workaround VS Code only supporting one default tsconfig.json
+  // Otherwise *.test.ts files would show errors in VS Code
+  // See https://stackoverflow.com/questions/57044697/how-to-use-different-tsconfig-file-for-test-files-in-vscode
+  "extends": "../tsconfig.test.json"
+}

tsconfig.json

@@ -7,7 +7,6 @@
     "noUnusedLocals": true,
     "noUnusedParameters": true,
     "outDir": "dist",
-    "baseUrl": ".",
     "sourceMap": true,
     "strict": true,
     "target": "es2021",