ng build with v13 silently fails

[ersimont]

🐞 Bug report

Command (mark with an x)

• [ ] new
• [X] build
• [ ] serve
• [ ] test
• [ ] e2e
• [ ] generate
• [ ] add
• [ ] update
• [ ] lint
• [ ] extract-i18n
• [ ] run
• [ ] config
• [ ] help
• [ ] version
• [ ] doc

Is this a regression?

Yes, the previous version in which this bug was not present was: 12 ### Description After upgrading from 12.0.0 to 13.0.0-rc.1, for one of my projects `ng build project-name` fails quickly without printing any error message to help me understand why, or what to fix. ## 🔬 Minimal Reproduction

git clone git@github.com:simontonsoftware/s-libs.git
cd s-libs
git checkout 22a81fcb83fefaa9a1e12ec63e7b7d0358ec4760
yarn
yarn ng build micro-dash

🔥 Exception or Error

$ ng build micro-dash
Building Angular Package
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

🌍 Your Environment

Angular CLI: 13.0.0-rc.1
Node: 14.18.1
Package Manager: yarn 1.22.15
OS: win32 x64

Angular: 13.0.0-rc.1
... animations, cdk, cli, common, compiler, compiler-cli, core
... forms, material, platform-browser, platform-browser-dynamic
... router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1300.0-rc.1
@angular-devkit/build-angular   13.0.0-rc.1
@angular-devkit/core            13.0.0-rc.1
@angular-devkit/schematics      13.0.0-rc.1
@schematics/angular             13.0.0-rc.1
ng-packagr                      13.0.0-rc.2
rxjs                            7.4.0
typescript                      4.4.4

Anything else relevant?

Nothing I know of.

[alan-agius4]

One of your tsconfig files contains errors

projects/micro-dash/tsconfig.lib.json:12:5 - error TS1005: ',' expected.

12     "noImplicitReturns": false
       ~~~~~~~~~~~~~~~~~~~

[ersimont]

🎉 Amazingly quick fix, and thank you for reporting back on my particular error!

[angular-automatic-lock-bot[bot]]

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.}