Arch Linux User Repository

@mdx as noted upstream, this package requires npm <7: https://github.com/balena-io/balena-cli/blob/master/package.json#L88

Why does this package depend on npm4 instead of npm? Edit: switched to balena-cli-bin package.

This package expects me downgrade to nodejs-lts-dubnium

nodejs-lts-dubnium and nodejs are in conflict. Remove nodejs

How can I make use of this package in multi nodejs environment ?

@anonumoouse according to https://wiki.archlinux.org/index.php/Arch_User_Repository#How_to_get_a_PKGBUILD_into_the_community_repository? a trusted user (TU) will need to adopt the package to get it into the community repository. Since this package has only 3 votes at the moment, I doubt any TU will be willing to adopt it at this point (that FAQ mentions a minimum of 10 votes generally).

Is there a reason none of the balena packages are in the arch linux community pkg repos? It's open source and popular. This package in particular takes forever to build on its very frequent updates. Wouldn't that be avoided if it was a normal arch pkg?

Just built it with Node v13, it's been supported since 11.25.10, see: https://github.com/balena-io/balena-cli/issues/1591

The package (actually a dependecy ext2fs) doesn't build with Node 13. This should be reflected in the nodejs dependency version restriction (`nodejs<13.0.0') until it is resolved upstream.

git is missing from makedepends. package fails with npm error output:

npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno ENOENT
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t ssh://git@github.com/balena-io-library/node-unzip-2.git
...