@planqk/planqk-cli
Advanced tools
The PlanQK Command Line Interface (CLI) lets you interact with the PlanQK Platform directly from your terminal. We have installation instructions to guide you through the initial setup in our quickstart guide.
Detailed information about the supported commands can be found in our CLI reference.
To install the PlanQK CLI, you must install Node.js and the npm command line interface using either a Node version manager or a Node installer.
Make sure you install Node.js version 18 or higher.
Then install the PlanQK CLI globally using npm:
npm install -g @planqk/planqk-cli
IMPORTANT: Make sure you have uninstalled the deprecated CLI:
npm uninstall -g @anaqor/planqk
You can use the --help flag to get information about the supported commands:
planqk --help
You may also get information about a specific command:
planqk <command> --help
Troubleshooting: If you experience EACCES permissions errors during installation, we recommend using Node version manager (nvm). Further, you may refer to the official npm documentation how to resolve such issues.
Apache-2.0 | Copyright 2023-2024 Kipu Quantum GmbH
FAQs
PlanQK Platform CLI
We found that @planqk/planqk-cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.