You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes monorepos can have dozens (if not hundreds) of packages. This makes filtering very cumbersome.
For example if we want to run the tests for all the frontend packages, and there are a dozen such packages, the pnpm command ends up with a dozen --filter args (unless the repo is strict about using consistent prefixes/suffixes).
If we add a pnpm.groups property array in each package.json, we could instead do pnpm --filter-group=frontend build without having to keep adding new package names into the frontend build command.
If this is something that interests people, I'd be more than happy to try to create a PR.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Sometimes monorepos can have dozens (if not hundreds) of packages. This makes filtering very cumbersome.
For example if we want to run the tests for all the frontend packages, and there are a dozen such packages, the pnpm command ends up with a dozen
--filter
args (unless the repo is strict about using consistent prefixes/suffixes).If we add a
pnpm.groups
property array in eachpackage.json
, we could instead dopnpm --filter-group=frontend build
without having to keep adding new package names into the frontend build command.If this is something that interests people, I'd be more than happy to try to create a PR.
Beta Was this translation helpful? Give feedback.
All reactions