Arch Linux User Repository

Ok, uninstalled after using nodejs-lts-jod, what a mess they want to make huh...

Thanks @b4shful I got it eventually working with the lts, but I will take what you said into consideration and be wary that other things may now stop working. So much for balena-etcher being something 'simple and easy'

Perhaps I upgraded the balena-ethecer by installing the first etcher-bin (that is miss functional) and after installing the balena-etcher.

no, I tried, currently, there seems no way to build it with nodejs.

Can we please not use a dependency on nodejs-lts-jod? Since it conflicts with the nodejs package, anyone who removes nodejs and installs nodejs-lts-jod (or agrees when an AUR helper asks to replace it) will then get stuck with an older nodejs version (albeit updated until October 2025, and with maintenance updates until April 2027). That will increasingly cause problems and incompatibilities as time goes on, and down the line could also expose people to security issues after jod's EOL.

I know whoever made this change probably just wanted to get the package to build, but may not have asked themselves "it built successfully, but at what cost?".

There are plenty of people who will spot something like this and steer clear of it (in my case, uninstalling this package), but there is also a subset of AUR users who are perhaps inexperienced and (despite warnings to the contrary) use the AUR as if it's just another repository without understanding what it actually is. It's worth considering that this change could cause problems to these users down the line and cause a lot of headaches, because they won't notice that their nodejs got swapped and by the time problems crop up they might have no idea what could have caused it. Of course not everything can cater to inexperienced users all the time, but I think here it's worth thinking about for everyone's sake... perhaps there's some way to get it working with the official nodejs package.

Error during upgrade

yay -S --sudoloop balena-etcher
 -> No AUR package found for nodejs-lts
 -> could not find all required packages: nodejs-lts

trying to install balena-etcher on CachyOS and get the following -

==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Starting build()... npm warn EBADENGINE Unsupported engine { npm warn EBADENGINE package: 'balena-etcher@1.19.25', npm warn EBADENGINE required: { node: '>=20 <21' }, npm warn EBADENGINE current: { node: 'v23.6.0', npm: '11.1.0' } npm warn EBADENGINE } npm warn EBADENGINE Unsupported engine { npm warn EBADENGINE package: 'etcher-sdk@9.1.2', npm warn EBADENGINE required: { node: '>=18 <22' }, npm warn EBADENGINE current: { node: 'v23.6.0', npm: '11.1.0' } npm warn EBADENGINE } npm warn skipping integrity check for git dependency ssh://git@github.com/balena-io-modules/unbzip2-stream.git npm warn deprecated xterm-addon-search@0.8.2: This package is now deprecated. Move to @xterm/addon-search instead. npm warn deprecated xterm-addon-fit@0.5.0: This package is now deprecated. Move to @xterm/addon-fit instead. npm warn deprecated xterm@4.19.0: This package is now deprecated. Move to @xterm/xterm instead. npm warn deprecated trim@0.0.1: Use String.prototype.trim() instead npm warn deprecated shortid@2.2.16: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm warn deprecated json-schema-ref-parser@6.1.0: Please switch to @apidevtools/json-schema-ref-parser npm warn deprecated gar@1.0.4: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm warn deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. npm warn deprecated asar@3.2.0: Please use @electron/asar moving forward. There is no API change, just a package name change npm warn deprecated @types/ajv-keywords@3.5.0: This is a stub types definition. ajv-keywords provides its own type definitions, so you do not need this installed. npm warn deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs npm warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.

added 2359 packages, and audited 2360 packages in 46s

386 packages are looking for funding run npm fund for details

56 vulnerabilities (3 low, 16 moderate, 34 high, 3 critical)

To address issues that do not require attention, run: npm audit fix

To address all issues (including breaking changes), run: npm audit fix --force

and it goes on and on and on...

Can you please fix this?

@xAsh @kelvie This package failed to be built with nodejs 23, see full log

yeah why pinning a specific version of node, when the latest just works?

Why does this require nodejs-lts-iron? It conflicts with nodejs on my system.