Différences avec npm​

Contraitement à npm, pnpm valide toutes les options. For example,pnpm install --target_arch x64 willfail as--target_arch is not a valid option forpnpm install.

However, some dependencies may use thenpm_config_ environment variable, whichis populated from the CLI options. Dans ce cas, vous disposez des options suivantes:

1. explicitly set the env variable:npm_config_target_arch=x64 pnpm install
2. force the unknown option with--config.:pnpm install --config.target_arch=x64

Options​

-C <path>, --dir <path>​

Run as if pnpm was started in<path> instead of the current working directory.

-w, --workspace-root​

Run as if pnpm was started in the root of theworkspaceinstead of the current working directory.

Commandes​

Pour plus d'informations, référez-vous à la documentation pour avoir la liste des commandes CLI. Voici une liste de commandes utiles, avec leur équivalence en npm, pour vous aider à démarrer :

When an unknown command is used, pnpm will search for a script with the given name,sopnpm run lint is the same aspnpm lint. If there is no script with the specified name,then pnpm will execute the command as a shell script, so you can do things likepnpm eslint (seepnpm exec).

Environment variables​

Some environment variables that are not pnpm related might change the behaviour of pnpm:

• CI

These environment variables may influence what directories pnpm will use for storing global information:

• XDG_CACHE_HOME
• XDG_CONFIG_HOME
• XDG_DATA_HOME
• XDG_STATE_HOME

You can search the docs to find the settings that leverage these environment variables.