Package Details: firebase-tools 11.12.0-1

Git Clone URL: https://aur.archlinux.org/firebase-tools.git (read-only, click to copy)
Package Base: firebase-tools
Description: The Firebase Command Line Tools
Upstream URL: https://github.com/firebase/firebase-tools
Keywords: firebase google
Licenses: MIT
Submitter: crasm
Maintainer: 0x9fff00
Last Packager: sudoforge
Votes: 12
Popularity: 0.000030
First Submitted: 2017-03-24 00:42 (UTC)
Last Updated: 2022-10-01 14:46 (UTC)

Pinned Comments

sudoforge commented on 2020-11-28 23:58 (UTC) (edited on 2021-10-08 10:04 (UTC) by sudoforge)

PLEASE NOTE

This PKGBUILD is maintained on GitHub. Please use the following repository to submit patches, ask questions, and raise issues:

https://github.com/sudoforge/pkgbuilds

Latest Comments

1 2 Next › Last »

sudoforge commented on 2021-03-24 01:55 (UTC)

@christoph.gysin -- as this is an adopted package, I'm not too familiar with why the original author added the --user root option in the first place. I use this tool in a very limited capacity (dynamic links) and don't have the time to dedicate to testing it in depth.

Can you provide some context as to why you are making this suggestion?

christoph.gysin commented on 2021-03-23 20:50 (UTC)

Please remove --user root to avoid installing the root npm module

sudoforge commented on 2020-11-28 23:58 (UTC) (edited on 2021-10-08 10:04 (UTC) by sudoforge)

PLEASE NOTE

This PKGBUILD is maintained on GitHub. Please use the following repository to submit patches, ask questions, and raise issues:

https://github.com/sudoforge/pkgbuilds

sudoforge commented on 2020-11-28 23:58 (UTC)

Hey folks, I've just adopted this package and will be updating it shortly.

bjesus commented on 2020-11-24 09:06 (UTC)

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

aashiks commented on 2020-06-23 08:53 (UTC)

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

rdoursenaud commented on 2020-04-27 19:54 (UTC)

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

toddejohnson commented on 2020-04-20 18:03 (UTC)

Why does this have a bunch of 777 files?

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

sysroot commented on 2019-07-29 17:42 (UTC)

To help if you want I can be the new maintainer

sysroot commented on 2019-04-18 06:40 (UTC)

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}/" }