Respect ignorePatterns when finding packages in certain cases #1149
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.
In repos that don't use a supported monorepo manager (npm/yarn/pnpm workspaces, rush, lerna), respect
ignorePatternswhen globbing forpackage.jsonfiles. The intended use for this is a repo likebeachballthat's actually a single package, but it has test fixtures checked in which also containpackage.jsonfiles, and those fake packages should be ignored.This is NOT respected in the more common case of a monorepo with a recognized manager. To ignore those "real" packages, use the
scopeoption or set"private": truein package.json instead.I reused the same option for this instead of introducing a separate one like
packageIgnorePatternsbecause typically, you'd want to ignore changes in these same folders (e.g. fixtures) when determining changed packages. And adding another explicit package ignore option would be redundant withscope.Also update
workspace-toolsto 0.40.4.