feat(webpack-dev-server): update the generated tsconfig path for angular CT #27723
+17
−13
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.
Additional details
This changes is needed so that Nx users can execute
component-test
tasks inparallel
. This is a Huge performance blocker at the moment. This PR in version 13 unblocked users from doing this forReact
. However, this PR is needed to support this behavior for Angular (in addition to the other PR).Essentially when Component Testing for Angular is launched we generate a
tsconfig
file on the fly in a temp directory that gets passed to the Angular builder. The builder returns awebpack
config which we use in ourwebpack-dev-server
. The issue is that when Nx users try to run inparallel
the generatedtsconfig
file gets overwritten in the same path. This PR generates the temporarilytsconfig
in a unique path based upon theprojectRoot
name.Steps to test
How has the user experience changed?
No changes are made to the current UX. The change is that it now allows users with Nx to run in CT tests in parallel.
PR Tasks
cypress-documentation
?type definitions
?