fix(node): explicitly check that project is a library before updating imports #19040
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.
This PR fixes an issue where projects that have no type (e.g.
application
orlibrary
) cause the move/convert-to-monorepo generator to fail. You will see an error like this:This happens because non-library projects don't have an entry in tsconfig paths, so let's check that
projectType === 'library'
instead ofprojectType !== 'application'
.Also, update the node app generator to set
e2e
project astype: 'application'
, which caused this issue to surface.Current Behavior
move and convert-to-monorepo generators fail when project type is undefined.
Expected Behavior
move and convert-to-monorepo generators work even if project type is undefined.
Related Issue(s)
Fixes #