yarnpkg / berry
- среда, 29 января 2020 г. в 00:19:22
TypeScript
📦 🐈 The active development trunk for Yarn 2 ⚒
Fast, reliable, and secure dependency management.
Yarn is a modern package manager split into various packages. Its novel architecture allows to do things currently impossible with existing solutions:
Consult the dedicated page for more details.
The documentation is being reworked to contain an updated content and a refreshed design, and the most up-to-date version can be found on the repository GitHub pages: next.yarnpkg.com
On top of our classic integration tests, we also run Yarn every day against the latest versions of the toolchains used by our community - just in case, really. Everything should be green!
| Toolchains | Tooling |
|---|---|
Clone this repository, then run the following commands:
yarn build:cliHow it works
After building the CLI your global yarn will immediately start to reflect your local changes. This is because Yarn will pick up the yarnPath settings in this repository's .yarnrc.yml, which is configured to use the newly built CLI if available.
Works out of the box!
Note that no other command is needed! Given that our dependencies are checked-in within the repository (within the .yarn/cache directory), you don't even need to run yarn install. Everything just works right after cloning the project, and is guaranteed to continue to work ten years from now
Those plugins typically come bundled with Yarn. You don't need to do anything special to use them.
yarn constraints [--fix].yarn dlx command.file: protocol within your dependencies.yarn init command.link: and portal: references as dependencies.yarn npm login, yarn npm publish, ...).yarn pack command.Although developed on the same repository as Yarn itself, those plugins are optional and need to be explicitly installed through yarn plugin import @yarnpkg/<plugin-name>.
exec: protocol within your dependencies.yarn stage command.yarn workspaces foreach command.Plugins can be developed by third-party entities. To use them within your applications, just specify the full plugin URL when calling yarn plugin import. Note that plugins aren't fetched from the npm registry at this time - they must be distributed as a single JavaScript file.
To create your own plugin, please refer to the documentation.
The following packages are generic and can be used in a variety of purposes (including to implement other package managers, but not only):
The following packages are meant to be used by Yarn itself, and probably won't be useful to other applications: