NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #4629 most downloaded on npm
> A simple utility to get the packages from a monorepo, whether they're using Yarn, npm, Lerna, pnpm, Bun or Rush
Last release 1 years ago
25 Jul 2025
Release timing varies
gaps range from 2 weeks to 1.2 years
Nearly every release is documented
notes for 13 of 13 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
13 releases · first in 2020
One column per quarter.
Updated dependencies [`2c06ac0`]:
Updated dependencies [`28c3ff4`, `28c3ff4`, `3cf8c4e`, `1763058`, `a00f5f7`, `ceeb7cb`, `f29df03`]:
#250 3cf8c4e Thanks @Andarist! - Fixed an issue with projects using npm workspaces being recognized as yarn projects
#242 1763058 Thanks @spanishpear! - This package is now published as a pure ESM package.
#244 f29df03 Thanks @Andarist! - Add "engines" field for explicit node version support. The supported node versions are >=20.0.0.
Updated dependencies [`361a34f`]:
#208 361a34f Thanks @benmccann! - Add git repository info to package.json
Updated dependencies [361a34f]:
### Patch Changes - #201 `3c9641c` Thanks @manzoorwanijk! - Fixed the error for getPackages when given a non-root directory
3c9641c Thanks @manzoorwanijk! - Fixed the error for getPackages when given a non-root directoryUpdated dependencies [`de0fff3`]:
de0fff3 Thanks @steve-taylor! - Restored support for Bolt monorepos.de0fff3]:
Updated dependencies [`bf586f5`]:
bf586f5 Thanks @elliot-nelson! - The getPackages and getPackagesSync methods now take an optional list of Tool implementations, allowing the caller to restrict the desired types of monorepo discovered, or provide a custom monorepo tool implementation.bf586f5]:
Updated dependencies [`a01efc9`, `a01efc9`, `7b9c4f6`, `f046017`]:
f046017 Thanks @Andarist! - Increased the transpilation target of the source files to node@14.x. At the same time added this as package.json#engines to explicitly declare the minimum node version supported by this package.a01efc9 Thanks @elliot-nelson! - The get-packages package now returns a slightly different structure. The old tool string has been replaced with a tool object, using the new Tool interface provided by @manypkg/tools. Each Package now contains both the absolute directory and relative directory path. Last, the root package has been renamed rootPackage and is optional, to support monorepos that do not contain a root package.### Patch Changes - #122 `7bd4f34` Thanks @fz6m! - Fixed getting correct packages in pnpm workspaces with exclude rules.
### Patch Changes - #110 `c521941` Thanks @maraisr! - Includes types dependencies for PackageJson type
`35fcc9c` #70 Thanks @jesstelford! - Add missing license field
35fcc9c #70 Thanks @jesstelford! - Add missing license field`a4db72a` #63 Thanks @evocateur! - Add support for Lerna monorepos
a4db72a #63 Thanks @evocateur! - Add support for Lerna monoreposa4db72a]:
`596d821` #55 Thanks @Andarist! - Ignore node_modules when glob searching for packages. This fixes an issue with package cycles.
`72a0112` #47 Thanks @tarang9211! - Initial release of @manypkg/get-packages. If you're migrating from get-workspaces, the most important changes are:
72a0112 #47 Thanks @tarang9211! - Initial release of @manypkg/get-packages. If you're migrating from get-workspaces, the most important changes are:
tool, packages and rootname field and the config property has been renamed to packageJsonSee the README for more information on the new API
72a0112]:
Your coding agent can read these notes before it upgrades. Set up the MCP server →