@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]

@manypkg/[email protected]

Minor Changes

• 41dc2df #35 Thanks @Noviny! - Add a workspaceFilter option to allow packages to be left out.

• 41dc2df #35 Thanks @Noviny! - Add new config option, which allows the user to specify the package.json fields they want to include

Patch Changes

• 41dc2df #35 Thanks @Noviny! - Include version field by default

@manypkg/[email protected]

Minor Changes

• 4fbc692 #32 Thanks @Noviny! - Add new config option, which allows the user to specify the package.json fields they want to include

Patch Changes

• 4fbc692 #32 Thanks @Noviny! - Include version field by default

@manypkg/[email protected]

Minor Changes

• 528bb72 #30 Thanks @mitchellhamilton! - Changed peer and dev dependency relationship check to only require that the upper bound of the dev dep range is within the peer dep range so that cases where the dev dep range allows versions lower than the lower bound of such as a peer dep with ^1.0.0 and dev dep with * are allowed and this fixes the regression in 0.8.1 where cases that should have been fine weren't like a peer dep with ^1.0.0 and a dev dep with ^1.1.0

@manypkg/[email protected]

Patch Changes

• dcbfa46: Fix an error with the new internal dependencies being "*", which was incompatible with the peerDependency check

@manypkg/[email protected]

Minor Changes

• 86bd46d: Add new check: INTERNAL_DEV_DEP_NOT_STAR

  This check moves internal devDependencies between packages to be * - so in a case where I had a package sunshine, which depends on internal package 'sun':

  {
    "name": "sunshine",
    "version": "1.0.0",
    "devDependencies": {
      "sun": "^1.0.0"
    }
  }

  we will now have:

  {
    "name": "sunshine",
    "version": "1.0.0",
    "devDependencies": {
      "sun": "*"
    }
  }

  This is because all internal dependencies are always linked if the version of the internal dependency is within the specified range(which is already enforced by Manypkg), and devDependencies are only relevant in local installs. Having set versions here caused packages to be patched when one of their devDependencies left the range, which was not strictly necessary.

@manypkg/[email protected]

Minor Changes

• c393d90: Initial release

@manypkg/[email protected]

Minor Changes

• 801a468: Add exec command that runs a command in every workspace

@manypkg/[email protected]

Minor Changes

• 2e39bfa: Improve fix for external dependency range mismatches