- #206
c2c4a3bThanks @bdkopen! - Fixmanypkg upgrade @scopeupgrading packages like@scope-something/a
-
#204
b56869aThanks @emmatown! - Allow dependecies to use theworkspace:protocol and support adding"workspaceProtocol": "require"to themanypkgconfig to require it. -
Updated dependencies [
3c9641c]:- @manypkg/get-packages@2.2.1
- #174
de0fff3Thanks @steve-taylor! - Restored support for Bolt monorepos.
- Updated dependencies [
de0fff3]:- @manypkg/get-packages@2.2.0
- #162
f046017Thanks @Andarist! - Increased the transpilation target of the source files tonode@14.x. At the same time added this aspackage.json#enginesto explicitly declare the minimum node version supported by this package.
-
#122
7bd4f34Thanks @fz6m! - Fixed getting correct packages in pnpm workspaces with exclude rules. -
Updated dependencies [
7bd4f34]:- @manypkg/get-packages@1.1.3
- #119
256297bThanks @marcodejongh! - Change external mismatch behaviour to suggest and fix to the most commonly used dependency range in the workspace. If all ranges are only used once it will pick the highest.
- Updated dependencies [
5f6cded]:- @manypkg/get-packages@1.1.2
dc2b0f9Thanks @mitchellhamilton! - Addedmanypkg.ignoredRulesconfig option
-
ad6dbf1#85 Thanks @with-heart! - Added the ability to use the exact package or directory name to target a package that is a substring of another with for theruncommand:If packages exist at
packages/pkg-aandpackages/pkg-a-1, targetpkg-ausing the exact directory name:yarn manypkg run packages/pkg-a
If packages are named
@project/package-aand@project/package-a-1, targetpackage-ausing the exact package name:yarn manypkg run @project/package-a
3f0ac13#77 Thanks @Andarist! - Fixed a typo in the reported error message for the peer and dev dep check
f2e890e#68 Thanks @mitchellhamilton! - Ignore invalid ranges on external dependencies to allow git and other types of dependencies and allow people to ignore the external mismatch rule for certain dependencies by making dependenciesnpm:^1.0.0instead of^1.0.0.
- Updated dependencies [
35fcc9c]:- @manypkg/get-packages@1.1.1
-
f8f60d9#67 Thanks @jesstelford! - Add package.json#manypkg config object:{ "manypkg": {} }To support setting a default branch for the INCORRECT_REPOSITORY_FIELD check/fix, a new config option can be set:
{ "manypkg": { "defaultBranch": "master" } }The default
defaultBranchis"master".
-
a4db72a#63 Thanks @evocateur! - Add support for Lerna monorepos -
Updated dependencies [
a4db72a]:- @manypkg/get-packages@1.1.0
3be8695#61 Thanks @mitchellhamilton! - Remove check requiring that all devDependencies must be*. This has been removed because pre-release versions are not satisfied by*which means that you previously couldn't use Manypkg, have internal devDependencies and have pre-releases
3594303#51 Thanks @tarang9211! - Use @manypkg/get-packages instead of get-workspaces internally
503f242#53 Thanks @NateRadebaugh! - Add special logic forINCORRECT_REPOSITORY_FIELDcheck to handle github repository separately from azure
d73628d#48 Thanks @mitchellhamilton! - Add repository field check which checks if a GitHub repo URL is in therepositoryfield in the rootpackage.jsonand if it is, checks that all of the packages have arepositoryfield which goes into the directory of the package.
447c580#45 Thanks @NateRadebaugh! - Add reference tomanypkg execto readme
c5275fbThanks @mitchellhamilton! - Show a more informative error when a package has no name
-
63cdae1#42 Thanks @tarang9211! - Addedmanypkg 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-aatpackages/pkg-aand@project/package-batpackages/pkg-awhich both have astartscript,manypkg runcan 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
packageandpkgaren't unique among the package names/directories:yarn manypkg run package start yarn manypkg run pkg start
- Updated dependencies [
0ed3f2b]:- find-workspaces-root@0.2.0
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.0and 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.0and a dev dep with^1.1.0
- dcbfa46: Fix an error with the new internal dependencies being "*", which was incompatible with the peerDependency check
-
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.
- 801a468: Add exec command that runs a command in every workspace
- 2e39bfa: Improve fix for external dependency range mismatches
- 89d7407: Exit with 0 when checks fail
- e1874c3: Fix checks not running
- e1874c3: Improve the range chosen by the peer dev dep fixer
- 594c153: Enable peer and dev dep check
- 50c7974: Run
yarnafter fixers that require it
- 0cfe667: Temporarily disable dev and peer dep relationship check
- 0cfe667: Fix some cases around getting the highest semver range
- 9ac6104: Add first implementation of add command
- 6d5cc67: Initial release