-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to frida-js #132
Comments
This was referenced Apr 22, 2024
baltpeter
added a commit
that referenced
this issue
Apr 22, 2024
Merged
baltpeter
added a commit
to tweaselORG/cyanoacrylate
that referenced
this issue
Apr 22, 2024
baltpeter
added a commit
to tweaselORG/cyanoacrylate
that referenced
this issue
Apr 22, 2024
baltpeter
added a commit
to tweaselORG/cli
that referenced
this issue
Apr 22, 2024
baltpeter
added a commit
that referenced
this issue
Apr 23, 2024
baltpeter
added a commit
to tweaselORG/cyanoacrylate
that referenced
this issue
Apr 23, 2024
baltpeter
added a commit
to tweaselORG/cli
that referenced
this issue
Apr 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, we are using https://github.com/frida/frida-node, which requires native binaries. That brings quite a few issues with (cf. e.g. #124 and #119).
As a band-aid for the linked issues, we'll require exactly Node 18 for the time being.
In the long run, that is not a nice solution. Luckily, there is now https://github.com/httptoolkit/frida-js which looks like it should solve exactly those problems. We should switch to that eventually.
The text was updated successfully, but these errors were encountered: