Labhansh Agrawal

the files from `build/Release` are used to run node-pty. The ones in `bin` are prebuilt ones. Do try the qemu builds as well.

Oh, great. Which one worked for you? also did you try the other one? We have 3 approaches cross compile - #7227 compile node-pty on qemu - [LabhanshAgrawal/hyper/actions/runs/5242933057#artifacts](https://github.com/LabhanshAgrawal/hyper/actions/runs/5242933057#artifacts) build everything...

I see, in that case I can just check using my vm. Can you test the armhf ones from https://github.com/LabhanshAgrawal/hyper/actions/runs/5243597523 on chroot though, I don't have any way to test...

my bad, please try the builds from https://github.com/LabhanshAgrawal/hyper/actions/runs/5258908433#artifacts it has both arm64 and armhf builds

pacman build added in #7272

@Tyriar I'm facing the same issue in Hyper, the first bad commit seems to be https://github.com/microsoft/node-pty/commit/ba424e16d615ae6bab43a67c0979702548cce3bb

can you try with the [ci build](https://github.com/vercel/hyper/actions/runs/157826845) once

Looks like this is still an issue. I tried using v9.4.0 and I'm still getting this `common.gypi not found` error. E.g. https://github.com/vercel/hyper/actions/runs/5271238701/jobs/9531822058

> @LabhanshAgrawal looks like it didn't use 9.4.0. From the logs: > > ``` > gyp ERR! node -v v18.16.0 > gyp ERR! node-gyp -v v9.3.1 > ``` > Weird,...

It was picking up v9.3.1 from global packages, setting it up to use the local one solved this. Anyone else facing similar issue on github actions, feel free to check...