heroku-cli
Advanced tools
The Heroku CLI is used to manage Heroku apps from the command line.
For more about Heroku see https://www.heroku.com/home
To get started see https://devcenter.heroku.com/start
This is the next generation Node-based Heroku CLI. The goals of this project were to make plugins more flexible, remove Ruby as a runtime dependency, and make the CLI faster.
It has identical functionality to the old Ruby CLI. Under the hood, it is a modular CLI made up of node.js plugins.
For more on developing plugins, read Developing CLI Plugins
For problems directly related to the CLI, add an issue on GitHub.
For other issues, submit a support ticket.
Developing the CLI locally requires node.
The bulk of the code for this project lives at heroku/cli-engine and its dependencies.
To run the CLI locally, use the ./bin/run script.
Alpha build note: To make the run script operable, you must use yarn >= 0.21.3. After the initial project yarn install, do the following:
cd ./node_modules/cli-engine
yarn install
yarn prepare
FAQs
CLI to interact with Heroku
We found that heroku-cli demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 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
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.