ドキュメントに関する現在のご利用体験についてお聞かせください。アンケートにご協力ください。
glab dependency-firewall pnpm
Run pnpm through the GitLab Dependency Firewall. (BETA)
Synopsis
Run the pnpm binary through the GitLab Dependency Firewall. The command checks each package download and upload against the policy for the current project, refuses blocked packages, and summarizes the results after the run.
The command uses your package manager’s registry or index configuration, and does not modify it.
All arguments are forwarded to pnpm verbatim.
This feature is in beta and might not be ready for production use. It might be unstable and breaking changes can occur outside of major releases. For more information, see https://docs.gitlab.com/policy/development_stages_support/.
glab dependency-firewall pnpm <pnpm args> [flags]Examples
# Install dependencies through the Dependency Firewall
glab dependency-firewall pnpm install
# Add a package through the Dependency Firewall
glab dependency-firewall pnpm add left-pad
Environment variables
HTTPS_PROXY: outbound proxy glab uses to reach package registries, plain-HTTP registries included. Credentials in the URL are sent to the proxy.
HTTP_PROXY: outbound proxy for plain-HTTP registries when HTTPS_PROXY is unset.
NO_PROXY: hosts glab reaches directly instead of through an outbound proxy.
npm_config_https_proxy, npm_config_proxy: proxy settings for pnpm. glab reads them first, so the outbound proxy can differ from HTTPS_PROXY and HTTP_PROXY.Options inherited from parent commands
-h, --help Show help for this command.Was this page helpful?