a0863d19ac
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 2m11s
CI/CD Pipeline / Frontend - Build, Test & Push (push) Has been cancelled
- Changed build script from `nest build` to `tsc -p tsconfig.build.json` - This ensures TypeScript path aliases (@domain/*, @application/*, @infrastructure/*) are properly resolved during compilation - tsc-alias then converts the resolved paths to relative imports in the output - Reverted tsconfig.json to original baseUrl: "./" configuration - Added explicit path aliases to tsconfig.build.json for clarity Root cause: NestJS's `nest build` command doesn't fully support TypeScript path aliases out of the box. Using `tsc` directly ensures proper path resolution. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
14 lines
316 B
JSON
14 lines
316 B
JSON
{
|
|
"$schema": "https://json.schemastore.org/nest-cli",
|
|
"collection": "@nestjs/schematics",
|
|
"sourceRoot": "src",
|
|
"compilerOptions": {
|
|
"deleteOutDir": true,
|
|
"webpack": false,
|
|
"tsConfigPath": "tsconfig.build.json",
|
|
"plugins": ["@nestjs/swagger"],
|
|
"assets": [],
|
|
"watchAssets": false
|
|
}
|
|
}
|