Arch Linux User Repository

This fails to build for me...

==> Starting package()...
npm ERR! code ENOENT
npm ERR! syscall lstat
npm ERR! path /home/user/.cache/yay/firebase-tools/pkg/firebase-tools/usr
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, lstat '/home/user/.cache/yay/firebase-tools/pkg/firebase-tools/usr'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2020-11-24T09_05_49_939Z-debug.log
==> ERROR: A failure occurred in package().
    Aborting...
error making: firebase-tools

bumping the version to 8.4.1 and the sha256sums to dfc15bfb0710069e460a34c3df0401ecfef6e1bb2bb1da0795d7284be870a0c3 works.

@toddejohnson Thanks for the suggestion. I have added the fixes to this release.

Why does this have a bunch of 777 files?

https://wiki.archlinux.org/index.php/Node.js_package_guidelines looks to have a fix.

To help if you want I can be the new maintainer

Please update!

Maintainer: Raphaël Doursenaud rdoursenaud@free.fr

Previous Maintainer: crasm crasm@firebase-tools.aur.yooz4sio.vczf.io

PKGBUILD structure copied from grunt-cli package

pkgname=firebase-tools pkgver=6.6.0 pkgrel=0 pkgdesc="The Firebase Command Line Tools" arch=('any') url="https://firebase.google.com/docs/cli/" license=('MIT') depends=('nodejs') makedepends=('npm') provides=('nodejs-firebase-tools') conflicts=('nodejs-firebase-tools') replaces=('nodejs-firebase-tools') install=${pkgname}.install source=("https://registry.npmjs.org/${pkgname}/-/${pkgname}-${pkgver}.tgz") noextract=(${pkgname}-${pkgver}.tgz) sha256sums=('dda41d80422eef3dfc6838755c7ca85c5e6cf4e2be5ae84a08887432a66c8b21')

package() { npm install -g --user root --prefix "${pkgdir}/usr" "${srcdir}/${pkgname}-${pkgver}.tgz" mkdir -p "${pkgdir}/usr/share/licenses/${pkgname}" ln -s "/usr/lib/node_modules/${pkgname}/LICENSE" "${pkgdir}/usr/share/licenses/${pkgname}/" }

I can, but I'm also not doing any sort of testing. It doesn't take long to bump the version and hash, but if I'm not using firebase and there's a breaking change, it'll be time-consuming to update the package.

Even if you aren't actively using firebase, can't you just update the version number when someone marks it as outdated?

I'm not actively using firebase anymore, so if anyone wants to take over the package, shoot me an email (see PKGBUILD).