not work on linux platform of the hello world

[yunfan]

i had been recommend of this project and the example made me very impressive , but i can not run that hello world example, the follow is a full log

jyf@mini:~/work/codetool/verify/perry-verify
$ ls
bun.lock  CLAUDE.md  hello.ts  index.ts  node_modules  package.json  package-lock.json  README.md  tsconfig.json
jyf@mini:~/work/codetool/verify/perry-verify
$ cat hello.ts 
console.log(`你好 世界`)
jyf@mini:~/work/codetool/verify/perry-verify
$ npx @perryts/perry compile hello.ts -o hello
[perry] The @perryts/perry-linux-x64 package is not installed.
This usually means npm skipped the optional dependency for linux-x64.
Try: npm install --force @perryts/perry-linux-x64
Or reinstall @perryts/perry with a matching npm (≥8.12) so os/cpu/libc selectors apply.
Underlying error: Cannot find module '@perryts/perry-linux-x64/bin/perry'
Require stack:
- /home/jyf/work/codetool/verify/perry-verify/node_modules/@perryts/perry/bin/perry.js
jyf@mini:~/work/codetool/verify/perry-verify
$ fastfetch 
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMNMMMMMMMMM    jyf@mini
MMMMMMMMMMNs..yMMMMMMMMMMMMMm: +NMMMMMMM    --------
MMMMMMMMMN+    :mMMMMMMMMMNo` -dMMMMMMMM    OS: MX Libretto 23.6 x86_64
MMMMMMMMMMMs.   `oNMMMMMMh- `sNMMMMMMMMM    Host: GT 370
MMMMMMMMMMMMN/    -hMMMN+  :dMMMMMMMMMMM    Kernel: Linux 6.14.8-1-liquorix-amd64
MMMMMMMMMMMMMMh-    +ms. .sMMMMMMMMMMMMM    Uptime: 10 days, 20 hours, 25 mins
MMMMMMMMMMMMMMMN+`   `  +NMMMMMMMMMMMMMM    Packages: 3101 (dpkg)
MMMMMMMMMMMMMMNMMd:    .dMMMMMMMMMMMMMMM    Shell: bash 5.2.15
MMMMMMMMMMMMm/-hMd-     `sNMMMMMMMMMMMMM    Display (U27N3R): 1440x2560 @ 60 Hz in 27" [External]
MMMMMMMMMMNo`   -` :h/    -dMMMMMMMMMMMM    Display (CHL3400): 3440x1440 @ 60 Hz in 34" [External]
MMMMMMMMMd:       /NMMh-   `+NMMMMMMMMMM    WM: i3 (X11)
MMMMMMMNo`         :mMMN+`   `-hMMMMMMMM    Cursor: DMZ-Black
MMMMMMh.            `oNMMd:    `/mMMMMMM    Terminal: tmux 3.3a
MMMMm/                -hMd-      `sNMMMM    CPU: AMD Ryzen AI 9 HX 370 w/ Radeon 890M (24) @ 2.00 GHz
MMNs`                   -          :dMMM    GPU: AMD Radeon 880M / 890M [Integrated]
Mm:                                 `oMM    Memory: 10.67 GiB / 27.02 GiB (39%)
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM    Swap: 2.26 GiB / 5.00 GiB (45%)
                                            Disk (/): 26.81 GiB / 114.79 GiB (23%) - ext4
                                            Disk (/home): 222.81 GiB / 273.18 GiB (82%) - ext4
                                            Local IP (eth1): 10.255.73.43/22
                                            Locale: zh_CN.UTF-8

                                                                    
                                                                    
jyf@mini:~/work/codetool/verify/perry-verify
$ 

also my npm is 11.3.0

[proggeramlug]

Thanks for the detailed repro @yunfan — that log was enough to pinpoint it.

Root cause: our @perryts/perry-linux-x64 manifest declares libc: ["glibc"]. npm filters that by reading process.report.getReport().header.glibcVersionRuntime, falling back to parsing /etc/os-release. On some Linux builds — particularly ones with custom kernels like the Liquorix 6.14 you're running on MX Linux — that glibcVersionRuntime field comes back empty, and the /etc/os-release fallback has no positive glibc marker (only a negative musl/alpine one). npm can't prove glibc, so it silently skips both the glibc and musl candidates, leaving @perryts/perry wrapper with nothing to require.resolve. I reproduced it locally by running npm install @perryts/perry --os=linux --cpu=x64 without --libc: zero platform packages installed, identical failure mode.

Fix (committed to main as ba46a78, ships as v0.5.118): dropped the libc: ["glibc"] constraint from the glibc Linux manifests entirely, matching what esbuild does. On glibc systems the package installs by default; on musl systems the libc: ["musl"] variant still wins, and the wrapper's runtime isMusl() check picks the right binary either way.

Should work for you out of the box once the next release publishes (I'll drop a note here when it does). Until then:

npm install --force @perryts/perry-linux-x64

will get you unblocked today.

---

If you're curious / want to confirm the diagnosis, this one-liner would show it:

node -e "console.log(JSON.stringify(process.report.getReport().header.glibcVersionRuntime))"

We expect that to print "" or null on your setup (that's what triggers the bug); on most glibc distros it prints something like "2.35".