Repository navigation
ng update --next leads to wrong tsconfig.lib.prod.json path #16444
Description
🐞 Bug report
Command (mark with an x)
- new
- build
- serve
- test
- e2e
- generate
- add
- update
- lint
- xi18n
- run
- config
- help
- version
- doc
Is this a regression?
nope, this is related to angular 9 migration
Description
When upgrading a library to angular 9, ie ng update @angular/cli @angular/core --next, angular.json is updated to reference tsconfig.lib.prod.json. The path is wrong, as it's missing a leading dot (.)
🔬 Minimal Reproduction
- clone https://github.com/mpalourdio/ng-http-loader
- run
ng update @angular/cli @angular/core --next - yarn build --prod
🔥 Exception or Error
Error: ENOENT: no such file or directory, lstat '/tsconfig.lib.prod.json'
🌍 Your Environment
Angular CLI: 9.0.0-rc.6
Node: 12.13.0
OS: linux x64
Angular: 9.0.0-rc.6
... cli, common, compiler, compiler-cli, core, language-service
... platform-browser, platform-browser-dynamic
Ivy Workspace: Yes
Package Version
------------------------------------------------------------
@angular-devkit/architect 0.900.0-rc.6
@angular-devkit/build-angular 0.900.0-rc.6
@angular-devkit/build-ng-packagr 0.900.0-rc.6
@angular-devkit/build-optimizer 0.900.0-rc.6
@angular-devkit/build-webpack 0.900.0-rc.6
@angular-devkit/core 9.0.0-rc.6
@angular-devkit/schematics 9.0.0-rc.6
@ngtools/webpack 9.0.0-rc.6
@schematics/angular 9.0.0-rc.6
@schematics/update 0.900.0-rc.6
ng-packagr 9.0.0-rc.3
rxjs 6.5.3
typescript 3.6.4
webpack 4.41.2
Anything else relevant?
Changing /tsconfig.lib.prod.json to ./tsconfig.lib.prod.json fixes the issue.
Generated configuration
"architect": {
"build": {
"builder": "@angular-devkit/build-ng-packagr:build",
"options": {
"tsConfig": "./tsconfig.lib.json",
"project": "./ng-package.json"
},
"configurations": {
"production": {
"tsConfig": "/tsconfig.lib.prod.json"
}
}
},
}
Activity
fix(@schematics/angular): blank root leads to wrong tsconfig.lib.prod…
fix(@schematics/angular): blank root leads to wrong tsconfig.lib.prod…
angular-automatic-lock-bot commentedon Jan 17, 2020
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
fix(@schematics/angular): blank root leads to wrong tsconfig.lib.prod…