@manypkg/[email protected]

Minor Changes

• 3594303 #51 Thanks @tarang9211! - Use @manypkg/get-packages instead of get-workspaces internally

@manypkg/[email protected]

Patch Changes

• 596d821 #55 Thanks @Andarist! - Ignore node_modules when glob searching for packages. This fixes an issue with package cycles.

@manypkg/[email protected]

Patch Changes

• 503f242 #53 Thanks @NateRadebaugh! - Add special logic for INCORRECT_REPOSITORY_FIELD check to handle github repository separately from azure

@manypkg/[email protected]

Major Changes

• 72a0112 #47 Thanks @tarang9211! - Initial release of @manypkg/get-packages. If you're migrating from get-workspaces, the most important changes are:

  • getPackages is a named export
  • getPackages only accepts a single argument which is the directory to search from
  • getPackages returns an object which has tool, packages and root
  • getPackages will search up from the directory passed in to find a project root rather than requiring the project root to be passed in
  • the package objects no longer have a name field and the config property has been renamed to packageJson

  See the README for more information on the new API

Patch Changes

• Updated dependencies [72a0112]:
  • @manypkg/[email protected]

@manypkg/[email protected]

Major Changes

• 72a0112 #47 Thanks @tarang9211! - Initial release of @manypkg/find-root

@manypkg/[email protected]

Minor Changes

• d73628d #48 Thanks @mitchellhamilton! - Add repository field check which checks if a GitHub repo URL is in the repository field in the root package.json and if it is, checks that all of the packages have a repository field which goes into the directory of the package.

@manypkg/[email protected]

Patch Changes

• 447c580 #45 Thanks @NateRadebaugh! - Add reference to manypkg exec to readme

• c5275fb Thanks @mitchellhamilton! - Show a more informative error when a package has no name

[email protected]

Minor Changes

• 0ed3f2b #39 Thanks @Andarist! - Added support for finding pnpm workspace packages.

@manypkg/[email protected]

Minor Changes

• 0ed3f2b #39 Thanks @Andarist! - Added support for finding pnpm workspace packages.

Patch Changes

• Updated dependencies [0ed3f2b]:
  • [email protected]

@manypkg/[email protected]

Minor Changes

• 63cdae1 #42 Thanks @tarang9211! - Added manypkg run <partial package name or directory> <script> which can be used to execute scripts for packages within a monorepo.

  As an example, let's say there are two packages: @project/package-a at packages/pkg-a and @project/package-b at packages/pkg-a which both have a start script, manypkg run can be used like this:

  yarn manypkg run pkg-a start
  yarn manypkg run a start
  yarn manypkg run package-a start
  yarn manypkg run @project/package-a start
  yarn manypkg run packages/pkg-a start
  yarn manypkg run package-b start
  yarn manypkg run b start

  The following wouldn't work though because the package and pkg aren't unique among the package names/directories:

  yarn manypkg run package start
  yarn manypkg run pkg start

• 0ed3f2b #39 Thanks @Andarist! - Added support for finding pnpm workspace packages.

Patch Changes

• Updated dependencies [0ed3f2b]:
  • [email protected]