Arch Linux User Repository

I have switched the source back to the official GitHub release (now supporting x86_64 and aarch64 architectures).

Instead of creating a symlink to the JS entrypoint directly, we are now reusing the official startup script (bin/qwen), and patching it to use the system-wide Node.js.

This ensures that our execution behavior aligns as closely as possible with the official upstream release, and prevents the package from breaking in the future if upstream decides to change their internal entry points or file structures.

@gunit cli.js lost its shebang in a recent upstream release. The package.json bin entry is cli-entry.js, which has the proper #!/usr/bin/env node shebang. Should be fixed now — the symlink now points to cli-entry.js.

I can't start qwen 0.19.8-1. My errors (only on german): /usr/bin/qwen: Zeile 1: //: Ist ein Verzeichnis /usr/bin/qwen: Zeile 2: use strict: Kommando nicht gefunden ^C/usr/bin/qwen: Zeile 4: initCpuProfiler: Kommando nicht gefunden /usr/bin/qwen: Zeile 5: Syntaxfehler beim unerwarteten Symbol »}« /usr/bin/qwen: Zeile 5: `} from "./chunks/chunk-MJKEQSZI.js";'

And my patch:

diff --git a/PKGBUILD b/PKGBUILD
index 6b12fc8..c9baa28 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -24,9 +24,10 @@ package() {

   cp -a "${srcdir}/package/." "${appdir}/"
   rm -rf "${appdir}/vendor/ripgrep"
-  chmod 755 "${appdir}/cli.js"
-  ln -s "../lib/${_pkgname}/cli.js" "${pkgdir}/usr/bin/${_name}"

+  echo "/usr/bin/node --expose-gc  /usr/lib/qwen-code/cli.js" > "$pkgdir/usr/bin/qwen"
+  chmod 755 "$pkgdir/usr/bin/qwen"
+  
   rm -f "${appdir}/LICENSE"
   rm -f "${appdir}/README.md"
   install -Dm644 "${srcdir}/package/LICENSE" "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"

If you're unsure, I recommend sticking to the official qwen-code in the Extra repo. I originally created this package before the official one existed.

The main differences of this -bin package are:

• Source: The official package builds from Git; this one repacks the pre-built npm tarball.
• Auto-updates: Disables the built-in updater via a custom system-defaults.json.
• Debundled ripgrep: Removes the bundled ripgrep in favor of the system-wide one, reducing package size.
• Updates: May receive version updates slightly faster than the official package.

What is the benefit of using this AUR package over the "qwen-code" package in the Extra repository?

@guglovich Fixed. The problem was that the CLI was previously installed as a single file, but it expects bundled assets such as vendor/tree-sitter/*.wasm next to it. The package now uses the npm tarball and installs the full runtime layout, which should resolve the wasm path issue.

failed to asynchronously prepare wasm: Error: ENOENT: no such file or directory, open '/usr/bin/vendor/tree-sitter/tree-sitter.wasm' Aborted(Error: ENOENT: no such file or directory, open '/usr/bin/vendor/tree-sitter/tree-sitter.wasm')

the package with the official repo contains the same error. only the installation via npm helped