-
#231
aeb50f5
Thanks @VanTanev! - Upgradedpackage-json
,semver
andsembear
dependencies. -
#226
2fafd9a
Thanks @VanTanev! - Replacechalk
withpicocolors
-
#228
1cbdcb9
Thanks @VanTanev! - Remove thefind-up
dependency. -
#231
aeb50f5
Thanks @VanTanev! - Node.js version requirement raised to>= 18.0.0
-
#224
3c3198a
Thanks @VanTanev! - Replacespawndamnit
withtinyexec
for fewer dependencies -
#229
4a835ed
Thanks @VanTanev! - Updatevalidate-npm-package-name
to5.0.1
to remove one transitive dependency. -
#225
d0f4d92
Thanks @VanTanev! - Replacefs-extra
with nativenode:fs/promises
- #206
c2c4a3b
Thanks @bdkopen! - Fixmanypkg upgrade @scope
upgrading packages like@scope-something/a
-
#204
b56869a
Thanks @emmatown! - Allow dependecies to use theworkspace:
protocol and support adding"workspaceProtocol": "require"
to themanypkg
config to require it. -
Updated dependencies [
3c9641c
]:- @manypkg/[email protected]
- #174
de0fff3
Thanks @steve-taylor! - Restored support for Bolt monorepos.
- Updated dependencies [
de0fff3
]:- @manypkg/[email protected]
- #162
f046017
Thanks @Andarist! - Increased the transpilation target of the source files to[email protected]
. At the same time added this aspackage.json#engines
to explicitly declare the minimum node version supported by this package.
- Updated dependencies [
7b9c4f6
,f046017
,a01efc9
]:- @manypkg/[email protected]
-
#122
7bd4f34
Thanks @fz6m! - Fixed getting correct packages in pnpm workspaces with exclude rules. -
Updated dependencies [
7bd4f34
]:- @manypkg/[email protected]
- #119
256297b
Thanks @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/[email protected]
dc2b0f9
Thanks @mitchellhamilton! - Addedmanypkg.ignoredRules
config 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 therun
command:If packages exist at
packages/pkg-a
andpackages/pkg-a-1
, targetpkg-a
using the exact directory name:yarn manypkg run packages/pkg-a
If packages are named
@project/package-a
and@project/package-a-1
, targetpackage-a
using 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.0
instead of^1.0.0
.
- Updated dependencies [
35fcc9c
]:- @manypkg/[email protected]
-
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
defaultBranch
is"master"
.
-
a4db72a
#63 Thanks @evocateur! - Add support for Lerna monorepos -
Updated dependencies [
a4db72a
]:- @manypkg/[email protected]
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_FIELD
check to handle github repository separately from azure
d73628d
#48 Thanks @mitchellhamilton! - Add repository field check which checks if a GitHub repo URL is in therepository
field in the rootpackage.json
and if it is, checks that all of the packages have arepository
field which goes into the directory of the package.
447c580
#45 Thanks @NateRadebaugh! - Add reference tomanypkg exec
to readme
c5275fb
Thanks @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-a
atpackages/pkg-a
and@project/package-b
atpackages/pkg-a
which both have astart
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
andpkg
aren't unique among the package names/directories:yarn manypkg run package start yarn manypkg run pkg start
- Updated dependencies [
0ed3f2b
]:
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
- 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
yarn
after 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