feat(schematics): create local project tsconfigs for typings #922
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Behavior
Typings conflict and get overwritten when
jest
orcypress
are used.The only
tsconfig.json
(Which is the only filename IDEs/tsserver
will recognize) is in the root directory meaning the whole workspace is subject to the same configuration within the IDE.Expected Behavior
Local
tsconfig.json
files are created in every project root and define the appropriate types for each project. These files extend the roottsconfig.json
and are mainly responsible for typings.tsconfig.(app|lib|spec|e2e).json
files will extend off of the localtsconfig
A migration is written which will update existing
tsconfigs
and create new ones.I am drafting a wiki page here: https://github.com/FrozenPandaz/nx/wiki/Workspace-Organization#tsconfigs
Issue
Fixes #816