feat(source): handle negated globs in workspace configs

[richburdon]

Description

No apparent way to exclude globs from sources.
Additionally excluded patterns from pnpm-workspace.yml are ignored. E.g.,

packages:
  - `packages/**/*`
  - '!packages/skipped/**/*'

Suggested Solution

Should honor exclusion globs (and provide --exclude CLI option)

Help Needed

N/A

[JamieMason]

Hey @richburdon,
It looks like currently the globs are resolved by syncpack once at a time using glob.globSync.

Syncpack does provide the Ignored version group, which the ignore patterns could be duplicated into to ignore those same packages for now. That's duplication though and it's a good idea to have the negated patterns handled so it's all done at source (I've not seen anyone doing this before when defining workspaces, hence it being missing).

We use the official glob package which npm uses internally but it doesn't support negated globs. There is an ignore option we could look into using though for any globs starting with !, rather than switching from the official package to something like globby.

Thanks for raising this.

[richburdon]

Thanks for the quick response.

The issue is with a tool that is generating multiple (many) temp directories that each have package.json files (this is happening inside one of the excluded pnpm package folders). So, looking for a way to exclude other named folders.

[JamieMason]

Released in 10.6.1. Any problems, please let me know.

If you find syncpack useful, please star the project or help us spread the word to other Developers.