#project is not building
9 messages · Page 1 of 1 (latest)
[System Information]
OS Version : Linux 5.15.146.1-microsoft-standard-WSL2
NodeJS Version : v20.11.1
NPM Version : 10.2.4
[Nest CLI]
Nest CLI Version : 10.3.2
[Nest Platform Information]
platform-express version : 10.3.3
schematics version : 10.1.1
testing version : 10.3.3
common version : 10.3.3
core version : 10.3.3
cli version : 10.3.2
{
"compilerOptions": {
"composite": true,
"target": "ESNext",
"module": "ESNext",
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"moduleResolution": "Bundler",
"allowSyntheticDefaultImports": true,
"isolatedModules": false,
"resolveJsonModule": true,
"types": ["node"],
"outDir": "dist",
"noEmit": false,
"verbatimModuleSyntax": false,
"rootDir": "./src",
"skipLibCheck": true,
},
"include": ["./src"],
"exclude": ["node_modules"],
"ts-node": {
"esm": true,
"experimentalSpecifierResolution": "node"
}
}
I am getting tsconfig.build.tsbuildinfo generated which seems to be causing the issues because here what happenes exactly:
1 - building for the first time works
2 - nest build again will delete dist folder and won't build
3 - deleting tsbuildinfo and running nest build generates the dist folder
how can I solve this?
Why is your moduleResolution set to Bundler?
Usually, that tsconfig.build.tsbuildinfo is from an incremental option, IIRC, and I don;'t see that option in here
https://www.totaltypescript.com/tsconfig-cheat-sheet#building-for-a-library-in-a-monorepo
Seems like an unusual tsconfig mix for build. The tsbuildinfo is probably caused by composite: true, and rimraf dist is probably not enough for clean build?
I just followed the same structure as this project https://github.com/toeverything/AFFiNE/blob/canary/packages/backend/server/tsconfig.json didn't really notice what was the bundler used for there
I tried disabling incremental but it's still creating the file