Package Details: bitwarden-cli 1.15.1-1

Git Clone URL: (read-only, click to copy)
Package Base: bitwarden-cli
Description: The command line vault (Windows, macOS, & Linux).
Upstream URL:
Licenses: GPL3
Conflicts: bitwarden-cli-git
Submitter: StephenBrown2
Maintainer: libertylocked
Last Packager: libertylocked
Votes: 37
Popularity: 3.20
First Submitted: 2018-05-21 20:41
Last Updated: 2021-03-24 20:15

Latest Comments

1 2 3 Next › Last »

yochananmarqos commented on 2021-05-11 23:33

FYI, the last version of Node.js 10 (EOL as of 04/30/2021) is 10.24.1 while the PKGBUILD is using 10.24.0. The next version will use 14.

hannu commented on 2021-03-22 07:59

It would be nice to unset NPM_CONFIG_PREFIX while building. I'm getting this error:

==> Starting build()...
nvm is not compatible with the "NPM_CONFIG_PREFIX" environment variable: currently set to "some_value"
Run `unset NPM_CONFIG_PREFIX` to unset it.
==> ERROR: A failure occurred in build().

grawlinson commented on 2020-05-30 07:40

1.10.0 now has zsh completion, but it needs to be generated manually.

This is my PKGBUILD for reference:

# Maintainer: libertylocked <>
# Contributor: Stephen Brown II <Stephen [dot] Brown2 [at]>
# Contributor: George Rawlinson <>

pkgdesc="Command-line interface to manage a Bitwarden vault"
makedepends=(nodejs-lts-dubnium npm git python)

prepare() {
  rmdir "${srcdir}/cli-${pkgver}/jslib"
  ln -s "${srcdir}/jslib-${_jslibcommit}" "${srcdir}/cli-${pkgver}/jslib"

build() {
  # build binary
  cd "${srcdir}/cli-${pkgver}"
  npm install --cache "${srcdir}/npm-cache"
  npm run dist:lin

  # create zsh completions
  ./dist/linux/bw completion --shell zsh > _bw

package() {
  # package binary
  install -Dm755 -t "${pkgdir}/usr/bin" "${srcdir}/cli-${pkgver}/dist/linux/bw"

  # package zsh completions
  install -Dm644 -t "${pkgdir}/usr/share/zsh/site-functions" "${srcdir}/cli-${pkgver}/_bw"

grawlinson commented on 2020-02-25 09:30

agowa338: That's honestly a really strange error to run into. Thanks for posting a workaround. If this is not resolved upstream, it would be ideal if the maintainer for npm was made aware that git could be a runtime dependency.

Running namcap on the resulting package results in this warning also:

bitwarden-cli E: Dependency gcc-libs detected and not included (libraries ['usr/lib/', 'usr/lib/'] needed in files ['usr/bin/bw'])

I'm not too sure if I want to go any further down this rabbit hole, so I'll leave it at that!

agowa338 commented on 2020-02-23 11:45

For all that tried building this packet using makechrootpkg in a clean environment, there is one build dependency missing 'git', without it being installed, the build crashes using cb() never called

I currently don't know if this is a issue within the bitwarden-cli project or npm itself. I think it might be within npm itself, because of the unspecified error it causes, I would expect a more meaningful error message if it was invoked through the build steps.

Here is the corresponding issue at the npm repo:

libertylocked commented on 2019-12-13 08:13

Sorry for the delay. I updated the package to 1.8.0

djmattyg007 commented on 2019-11-17 05:07

Would be good to get an update on this package.

libertylocked commented on 2019-07-17 06:35

Maybe it only builds with node 10, I'm not sure. Anyway I've updated the PKGBUILD to use NVM to build. It should work now. Thanks for the report.

mvdan commented on 2019-07-17 02:01

I get failures involving "No available node version satisfies 'node11'". Which is a bit weird, as I have the latest nodejs package, 11.15.0-1. Any ideas? It seems like it's the package:lin script that caused the error.

libertylocked commented on 2019-07-16 06:54

Sorry it took this long. I've had some problems with runtime jsdom dependency. Now the build bundles nodejs in the bin which isn't ideal and adds a little bit to the install size, but it'll have to do for now.