frida has no prebuilt binaries for Node 20

[zner0L]

For node v20, the install fails because there are no prebuilt binaries for frida.

[zner0L]

There is a related issue in frida/frida-node#87

[baltpeter]

This appears to still be an issue, just go this on Node 20:

❯ yarn
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning "ipa-extract-info > zipjs-browserify > [email protected]" has unmet peer dependency "browserify@>= 2.3".
warning " > @typescript-eslint/[email protected]" has unmet peer dependency "@typescript-eslint/parser@^5.0.0".
[5/5] Building fresh packages...
[1/7] ⠄ frida
[2/7] ⠄ cpu-features
[-/7] ⠄ waiting...
[6/7] ⠄ lmdb
warning Error running install script for optional dependency: "/home/benni/coding/JS/tweasel/appstraction/node_modules/cpu-features: Command failed.
Exit code: 127
Command: node buildcheck.js > buildcheck.gypi && node-gyp rebuild
Arguments: 
Directory: /home/benni/coding/JS/tweasel/appstraction/node_modules/cpu-features
Output:
/bin/sh: 1: node-gyp: not found"
info This module is OPTIONAL, you can safely ignore this error
error /home/benni/coding/JS/tweasel/appstraction/node_modules/frida: Command failed.
Exit code: 127
Command: prebuild-install || node-gyp rebuild
Arguments: 
Directory: /home/benni/coding/JS/tweasel/appstraction/node_modules/frida

For now, we need to pin Node 18 exactly everywhere (instead of >= 18 like currently).

In the long term, the solution appears to once again be to switch to what HTTP Toolkit is doing. :) https://github.com/httptoolkit/frida-js

[baltpeter]

Closing in favour of #132.