Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/yarnpkg/example-repo-zipn below:

yarnpkg/example-repo-zipn: Just to check the size of the berry repository with compression N

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:

• Yarn supports plugins; adding a plugin is as simple as adding it into your repository
• Yarn supports Node by default but isn't limited to it - plugins can add support for other languages
• Yarn supports workspaces natively, and its CLI takes advantage of that
• Yarn uses a bash-like portable shell to make package scripts portable across of Windows, Linux, and macOS
• Yarn is first and foremost a Node API that can be used programmatically (via @yarnpkg/core)
• Yarn is written in TypeScript and is fully type-checked

Consult the Installation Guide.

Consult the Migration Guide.

The documentation can be found at yarnpkg.com.

The API documentation can be found at yarnpkg.com/api.

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. Everything should be green!

Consult the Contributing Guide.

Clone this repository, then run the following commands:

How 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.

• plugin-compat contains a few built-in patches applied to improve PnP support.
• plugin-constraints adds support for constraints to Yarn.
• plugin-dlx adds support for the yarn dlx command.
• plugin-essentials adds various commands deemed necessary for a package manager (add, remove, ...).
• plugin-exec adds support for using the exec: protocol within your dependencies.
• plugin-file adds support for using the file: protocol within your dependencies.
• plugin-git adds support for cloning packages from Git repositories.
• plugin-github adds support for using GitHub references as dependencies. This plugin doesn't use git.
• plugin-http adds support for using straight URL references as dependencies (tgz archives only).
• plugin-init adds support for the yarn init command.
• plugin-interactive-tools adds support for various interactive commands (yarn upgrade-interactive).
• plugin-link adds support for using link: and portal: references as dependencies.
• plugin-nm adds support for installing packages through a node_modules folder.
• plugin-npm adds support for using semver ranges dependencies, resolving them from an npm-like registry.
• plugin-npm-cli adds support for npm-specific commands (yarn npm login, yarn npm publish, ...).
• plugin-pack adds support for the yarn pack command.
• plugin-patch adds support for the patch: protocol.
• plugin-pnp adds support for installing JavaScript dependencies through the Plug'n'Play specification.
• plugin-stage adds support for the yarn stage command.
• plugin-typescript improves the user experience when working with TypeScript.
• plugin-version adds support for the new release workflow.
• plugin-workspace-tools adds support for the 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):

• @yarnpkg/core allows any application to manipulate a project programmatically.
• @yarnpkg/fslib is a set of tools to abstract the filesystem through type-safe primitives.
• @yarnpkg/libzip contains zlib+libzip bindings compiled to WebAssembly.
• @yarnpkg/nm contains the node_modules tree builder and hoister.
• @yarnpkg/parsers can be used to parse the language used by @yarnpkg/shell.
• @yarnpkg/pnp can be used to generate Plug'n'Play-compatible hooks.
• @yarnpkg/pnpify is a CLI tool to transparently add PnP support to various tools.
• @yarnpkg/sdks is a CLI tool to generate the PnP Editor SDKs.
• @yarnpkg/shell is a portable bash-like shell interpreter.

The following packages are meant to be used by Yarn itself, and probably won't be useful to other applications:

• @yarnpkg/builder contains a CLI tool to package berry and its plugins.
• @yarnpkg/cli is a CLI entry point built on top of @yarnpkg/core.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4