ai-workspace-services/qmd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #362 from syedair/fix/launcher-bun-install-false-positive

Browse Source 
fix: remove $BUN_INSTALL check from launcher to prevent false Bun detection
This commit is contained in:
Tobias Lütke 2026-03-10 21:38:41 -04:00 committed by GitHub
commit ae3604cb88
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
bin/qmd
View File

@ -15,8 +15,12 @@ done
# to avoid native module ABI mismatches (e.g., better-sqlite3 compiled for bun vs node)
DIR="$(cd -P "$(dirname "$SOURCE")/.." && pwd)"
# Check if we were installed with bun (look for bun.lock or bun-lockb)
if [ -f "$DIR/bun.lock" ] || [ -f "$DIR/bun.lockb" ] || [ -n "$BUN_INSTALL" ]; then
# Check if we were installed with bun (look for bun.lock or bun-lockb).
# $BUN_INSTALL is intentionally NOT checked here — it only indicates that bun
# exists on the system, not that it was used to install this package. When QMD
# is installed via npm, native modules are compiled for Node and running them
# under bun causes ABI mismatches (e.g. sqlite-vec "no such module: vec0").
if [ -f "$DIR/bun.lock" ] || [ -f "$DIR/bun.lockb" ]; then
exec bun "$DIR/dist/cli/qmd.js" "$@"
else
exec node "$DIR/dist/cli/qmd.js" "$@"