fix: correct TypeScript baseUrl to resolve path aliases during build
Some checks failed
CI/CD Pipeline / Integration Tests (push) Blocked by required conditions
CI/CD Pipeline / Deployment Summary (push) Blocked by required conditions
CI/CD Pipeline / Backend - Build, Test & Push (push) Failing after 2m5s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Has been cancelled
Some checks failed
CI/CD Pipeline / Integration Tests (push) Blocked by required conditions
CI/CD Pipeline / Deployment Summary (push) Blocked by required conditions
CI/CD Pipeline / Backend - Build, Test & Push (push) Failing after 2m5s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Has been cancelled
Changed baseUrl from "./" to "./src" and updated paths to be relative to src directory. This allows TypeScript to correctly resolve imports using @domain/*, @application/*, and @infrastructure/* aliases during compilation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
parent
d649f17714
commit
e1e9b605cc
@ -9,7 +9,7 @@
|
|||||||
"target": "ES2021",
|
"target": "ES2021",
|
||||||
"sourceMap": true,
|
"sourceMap": true,
|
||||||
"outDir": "./dist",
|
"outDir": "./dist",
|
||||||
"baseUrl": "./",
|
"baseUrl": "./src",
|
||||||
"incremental": true,
|
"incremental": true,
|
||||||
"skipLibCheck": true,
|
"skipLibCheck": true,
|
||||||
"strictNullChecks": true,
|
"strictNullChecks": true,
|
||||||
@ -23,9 +23,9 @@
|
|||||||
"resolveJsonModule": true,
|
"resolveJsonModule": true,
|
||||||
"esModuleInterop": true,
|
"esModuleInterop": true,
|
||||||
"paths": {
|
"paths": {
|
||||||
"@domain/*": ["src/domain/*"],
|
"@domain/*": ["domain/*"],
|
||||||
"@application/*": ["src/application/*"],
|
"@application/*": ["application/*"],
|
||||||
"@infrastructure/*": ["src/infrastructure/*"]
|
"@infrastructure/*": ["infrastructure/*"]
|
||||||
}
|
}
|
||||||
},
|
},
|
||||||
"include": ["src/**/*"],
|
"include": ["src/**/*"],
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user