Motivación
Ahorro de espacio en disco#
Cuando usas npm, las dependencias se instalan en almacenamientos individuales, lo que provoca que descargues la misma dependencia por cada proyecto que dependa de esta. Con pnpm, esa dependencia sera almacenada en un almacenamiento compartido, así:
- Si dependes de diferentes versiones de una dependencia, solo los archivos que difieren serán agregados al almacenamiento. For instance, if it has 100 files, and a new
version has a change in only one of those files,
pnpm updatewill only add 1 new file to the store, instead of cloning the entire dependency just for the singular change. - Todos los archivos son guardados en un solo lugar del disco duro. When packages are
installed, their files are hard-linked or cloned (copy-on-write) from that single
place, consuming no additional disk space. By default, pnpm copies files only
when the filesystem supports neither. See
packageImportMethod. Esto te permitirá compartir tus dependencias de la misma version en diferentes proyectos.
As a result, you save a lot of space on your disk proportional to the number of projects and dependencies, and you have a lot faster installations.
Aumentar la velocidad de instalación#
pnpm performs installation in three stages:
- Resolución de dependencias. Todas las dependencias requeridas se identifican y se llevan al almacenamiento.
- Cálculo de estructura de directorios. The
node_modulesdirectory structure is calculated based on the dependencies. - Enlazar dependencias. All remaining dependencies are fetched and hard linked from the store to
node_modules.
Each package moves to the next stage as soon as it is ready, without waiting for the other packages. This is faster than the traditional three-stage installation process, which resolves all dependencies, then fetches all of them, then writes all of them to node_modules.
Creating a non-flat node_modules directory#
When installing dependencies with npm or Yarn Classic, all packages are hoisted to the root of the modules directory. As a result, source code has access to dependencies that are not added as dependencies to the project.
By default, pnpm uses symlinks to add only the direct dependencies of the project into the root of the modules directory.
If you'd like more details about the unique node_modules structure that pnpm
creates and why it works fine with the Node.js ecosystem, read:
tip
If your tooling doesn't work well with symlinks, you may still use pnpm and set the nodeLinker setting to hoisted. This will instruct pnpm to create a node_modules directory that is similar to those created by npm and Yarn Classic.