Configurational Dependencies in pnpm

PNPM version 10 introduced a new type of dependency called config dependencies, which allows users to create custom plugins and modify PNPM's behavior during runtime.

Config dependencies are installed before all other types of dependencies and allow users to plug into how PNPM works. They cannot have dependencies of their own and do not run lifecycle scripts. They can be added using the 'pmpm-add-config' command.

PNPM uses a central content addressable store, which allows Node modules to be hard linked to files in this store, reducing disk space usage. It is also well-suited for monorepos.

Yes, config dependencies can be used to publish and manage patch files across multiple repositories, avoiding the need to copy patch files manually.

While config dependencies are limited and cannot have their own dependencies, users should still be cautious as they can be malicious. It is important to verify the safety of these packages.

PNPM hooks, such as update.config and read package hooks, allow users to modify PNPM configurations and package manifests during installation, enabling customization and better management of dependencies.

Although PNPM does not have built-in tools for migration from npm workspaces, there are third-party tools and Codemods that can assist in the migration process.

The 'P' in PNPM stands for 'performant', highlighting its efficiency as a package manager.

BIT uses PNPM under the hood for installation, benefiting from its features for dependency management, and allowing BIT to work on PNPM features as well.

In BIT, environment components are a type of dependency that allows portability and independence for each component, similar to how PNPM config dependencies work.