fix: npm-app build to use relative paths for common module

- Install tsc-alias to resolve TypeScript path mappings to relative paths
- Reorder build steps to copy dependencies before running tsc-alias
- Ensures published npm package uses correct relative imports instead of module paths

Author: brandonkachen

bun.lock

@@ -18,11 +18,11 @@
         "commands": [
           "eslint src/index.ts",
           "tsc",
-          "tsc-alias -p tsconfig.json",
           "mkdir -p dist/common",
           "cp -r ../common/dist/* dist/common",
           "mkdir -p dist/code-map",
           "cp -r ../packages/code-map/dist/* dist/code-map",
+          "tsc-alias -p tsconfig.json",
           "mkdir -p dist/utils/__tests__",
           "cp -r src/utils/__tests__/*.txt dist/utils/__tests__"
         ],

npm-app/project.json

@@ -55,6 +55,7 @@
     "prettier": "3.3.2",
     "ts-node": "^10.9.2",
     "ts-pattern": "^5.5.0",
+    "tsc-alias": "^1.8.16",
     "tsconfig-paths": "4.2.0",
     "types": "^0.1.1",
     "typescript": "5.5.4",