New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(misc): support workspaces using a root tsconfig.json instead of tsconfig.base.json #9195
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nrwl/nx-dev/63Hzqex68s9NBcBNLFGDHGMhTsdy [Deployment for 1454a02 canceled] |
f6e2fec
to
ae84691
Compare
ae84691
to
67ccbcc
Compare
67ccbcc
to
7996a79
Compare
packages/angular/src/generators/application/lib/create-files.ts
Outdated
Show resolved
Hide resolved
1da8cab
to
1454a02
Compare
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
There are several places within Nx where it doesn't fall back to locate a root
tsconfig.json
if the expectedtsconfig.base.json
doesn't exist.Most of the time this should be fine since Nx workspaces by default use
tsconfig.base.json
, but there are still some scenarios where atsconfig.json
might still be used (e.g. devs decide to use it, or Angular CLI workspaces migrated using a package likemake-angular-cli-faster
or Angular CLI workspaces migrated using the--preserve-angular-cli-layout
flag).Expected Behavior
The functionality within Nx should look for a root
tsconfig.json
if thetsconfig.base.json
file doesn't exist. By default,tsconfig.base.json
should still be used for everything and it's still the recommended file to use, but a fallback should be in place.Related Issue(s)
Fixes #