![require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages](https://cdn.sanity.io/images/cgdhsj6q/production/be8ab80c8efa5907bc341c6fefe9aa20d239d890-1600x1097.png?w=400&fit=max&auto=format)
Security News
require(esm) Backported to Node.js 20, Paving the Way for ESM-Only Packages
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
bitbucket-cli-plus
Advanced tools
Interface with Bitbucket via their RESTful api with the command line tool.
This version is a fork of Liam Moat's excellent original Bitbucket CLI, with a few differences:
Note: This tool is not affliated with Bitbucket or Atlassian. It is a third party library that simply interfaces with Bitbucket's API.
The Bitbucket CLI is installed and managed via npm, the Node.js package manager.
Before setting up ensure that your npm is up-to-date by running npm update -g npm
(this might require sudo on certain systems).
In order to get started, you'll want to install the command line interface (CLI) globally. You may need to use sudo (for OSX, *nix, BSD etc) or run your command shell as Administrator (for Windows) to do this.
npm install -g bitbucket-cli-plus
This will put the bitbucket
command in your system path, allowing it to be run from any directory.
To confirm it has installed correctly run bitbucket --version
.
The CLI uses OAuth when communicating with Bitbucket. Before using the CLI you need to obtain a consumer key and secret.
Bitbucket explain how to do this here.
Once the CLI is installed you're good go. Get all the available commands with bitbucket --help
.
There are three ways of giving the CLI you consumer settings:
export BITBUCKET_KEY="MY_CONSUMER_KEY"
export BITBUCKET_SECRET="MY_CONSUMER_SECRET"
bitbucket ...
BITBUCKET_KEY="MY_CONSUMER_KEY" BITBUCKET_SECRET="MY_CONSUMER_SECRET" bitbucket ...
bitbucket init
. This will prompt you for not only the key and secret, but also (optionally) the project slug and owner.This version of the Bitbucket CLI has an optional preference file that can be included in any directory at or above the project (local), or with the install of Bitbucket CLI itself (global). The options passed into the CLI are preferred to the environment variables, the environment variables to the local preferences, local preferences to global preferences, and finally, the global preferences are preferred over some pre-selected (hopefully sane) defaults, limited for now to v1 functionality. The following describes how and when the preferences are set and saved:
init
.init
.init
or as an argument for -o, --owner
coupled with --save
.init
or as an argument for -s, --slug
coupled with --save
.--save
for an issue subcommand, or as an argument for --kind
in an issue subcommand. Defaults to enhancement
.--save
for an issue subcommand, or as an argument for --priority
in an issue subcommand. Defaults to major
.--save
for an issue subcommand, or as an argument for --status
in an issue subcommand. Defaults to new
.0.1.4
FAQs
CLI for Bitbucket.org
The npm package bitbucket-cli-plus receives a total of 3 weekly downloads. As such, bitbucket-cli-plus popularity was classified as not popular.
We found that bitbucket-cli-plus demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
Security News
PyPI now supports iOS and Android wheels, making it easier for Python developers to distribute mobile packages.
Security News
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.