Still failing with:
error heroku@10.0.2: The engine "node" is incompatible with this module. Expected version "~20.x". Got "23.4.0"
Any chance the maintainer can update the Pkgbuild? This is getting tiresome to manually fix each update.
Git Clone URL: | https://aur.archlinux.org/heroku-cli.git (read-only, click to copy) |
---|---|
Package Base: | heroku-cli |
Description: | CLI to manage Heroku apps and services with forced auto-update removed |
Upstream URL: | https://devcenter.heroku.com/articles/heroku-cli |
Licenses: | custom, ISC |
Conflicts: | heroku-cli-bin, heroku-client-standalone, heroku-toolbelt, ruby-heroku |
Provides: | heroku, heroku-cli |
Submitter: | Redrield |
Maintainer: | rnestler (ChloeColman) |
Last Packager: | rnestler |
Votes: | 77 |
Popularity: | 1.30 |
First Submitted: | 2017-08-15 23:19 (UTC) |
Last Updated: | 2025-01-27 18:01 (UTC) |
Still failing with:
error heroku@10.0.2: The engine "node" is incompatible with this module. Expected version "~20.x". Got "23.4.0"
Any chance the maintainer can update the Pkgbuild? This is getting tiresome to manually fix each update.
The commit with version 10.0.2 fails to build with the same error as noted earlier:
error heroku@10.0.2: The engine "node" is incompatible with this module. Expected version "~20.x". Got "23.4.0"
error Found incompatible module.
The patch from @rharish still works.
Thanks @jackro, I looked at your fix, and using that, I managed to make a fix without adding a new makedependency:
diff --git a/PKGBUILD b/PKGBUILD
index ff59213..f65a6d1 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -43,6 +43,7 @@ prepare() {
# final installation
mv package heroku
pushd heroku
+ sed -i 's/"node": "~20\.x"/"node": ">=20"/' ./package.json
yarn --prod
popd
I was able to fix the build errors with https://github.com/jackrosenthal/pkgbuild/commit/fe517909aa12c7a0c4e51622f0ab10d130f544b6
Build fails with error:
error heroku@10.0.0: The engine "node" is incompatible with this module. Expected version "~20.x". Got "23.4.0"
error Found incompatible module.
The upstream git repo contains a .tool-versions
file. This makes the build fail for us that have asdf
installed, unless we already have the specific node version listed in there (currently node 16). The package should use the distro's nodejs anyway.
I had to add rm .tool-versions
to PKGBUILD after the pushd "cli"
line in prepare()
to make it work.
9.0.0 freezes on link step
I've adopted the Heroku-cli-bin package, I'd be happy to pitch in here as well if you're looking for someone to (help) maintain!
Sure! I'll add you as a maintainer.
I've adopted the Heroku-cli-bin package, I'd be happy to pitch in here as well if you're looking for someone to (help) maintain!
Cannot build with yarn-berry
, which makes sense as all commands in the PKGBUILD
assume yarn v1. It looks like Arch treats yarn-berry
as being synonymous with yarn
, which is not true at all.
If you have trouble building this package, make sure yarn -v
returns v1. If it doesn't, uninstall your yarn dependency and install yarn
and try again.
Pinned Comments