Error installing Grapefruit

[hongsolo9]

Hello @ChiChou

Not sure what to make of this error log. All running fine until line 278

278 verbose stack Error: command failed
278 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:53:27)
278 verbose stack     at ChildProcess.emit (node:events:519:28)
278 verbose stack     at maybeClose (node:internal/child_process:1105:16)
278 verbose stack     at Socket.<anonymous> (node:internal/child_process:457:11)
278 verbose stack     at Socket.emit (node:events:519:28)
278 verbose stack     at Pipe.<anonymous> (node:net:337:12)
279 verbose pkgid [email protected]
280 verbose cwd /Users/xxx/local/apps/frida/Grapefruit
281 verbose Darwin 21.6.0
282 verbose node v21.4.0
283 verbose npm  v10.2.4
284 error code 1
285 error path /Users/xxx/local/apps/frida/Grapefruit/node_modules/frida
286 error command failed
287 error command sh -c prebuild-install || node-gyp rebuild
288 error prebuild-install warn install No prebuilt binaries found (target=21.4.0 runtime=node arch=x64 libc= platform=darwin)
288 error gyp info it worked if it ends with ok

Any ideas where to start debugging would be helpful.

[OmkarAnekar]

Hello @hongsolo9

Is it a node project or a python project... As I know 'Grapefruit' is a Python library...

[ChiChou]

Sorry it's not a problem that could be solved easily. I need to upgrade the frida dependency and publish a new version. However the node echo system just evolve too radically, so the current codebase on vue2 won't build anymore. To completely rewrite everything in vue3 takes too much time, I can't guarantee if that's even possible.

[hongsolo9]

Thanks for getting back, @ChiChou. Will take a deeper look.

[gbergeson]

~~I'm running into a similar error, both when I attempt to install from npm and when I npm install after cloning the repo. @hongsolo9 , did you find a solution?~~

Apologies for the bump on this thread, my issue ended up being solved by the troubleshooting article linked in the README. I initially thought that it was a separate issue, but upon revisiting realized it was the same.