We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
我在尝试 npm install 的时候出现了这个。 是因为 node 版本还是其他原因吗? 希望大佬能够解答
npm ERR! code 1 npm ERR! path C:\Users\hp\Desktop\android\unity\frida\GameSentry-main\node_modules\frida npm ERR! command failed npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c prebuild-install || node-gyp rebuild npm ERR! prebuild-install WARN install connect ECONNREFUSED 223.75.236.241:443 gyp: binding.gyp not found (cwd: C:\Users\hp\Desktop\android\unity\frida\GameSentry-main\node_modules\frida) while trying to load binding.gyp npm ERR! gyp ERR! configure error npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1 npm ERR! gyp ERR! stack at ChildProcess.onCpExit (C:\Users\hp\Desktop\android\unity\frida\GameSentry-main\node_modules\node-gyp\lib\configure.js:325:16) npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:513:28) npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:291:12) npm ERR! gyp ERR! node -v v18.13.0 npm ERR! gyp ERR! node-gyp -v v9.3.1 npm ERR! gyp ERR! not ok
The text was updated successfully, but these errors were encountered:
hi,你可以参考以下两个链接解决这个问题 nodejs/node-gyp#1709 https://blog.csdn.net/StillCity/article/details/77483085 希望对你有帮助
Sorry, something went wrong.
好像是 "frida": "^14.2.8" 这个依赖的问题, 在 frida 中的 issues 也有人有这样的问题 但遗憾的是我并没有找到合适的解决方案。 大致意思是要 编译 frida/binding.gyp 但对于我来说好像有点额外的困难。
不过好在目前我可以拿大佬一部分代码 只用 python 启动firda 可以解决我部分需求。 但是没办法用到界面,来理解其余代码的使用
frida/frida#556 也有可能是网络问题
我用14.2.18死活编译不成功 换了新版本就可以编译成功 可以试试新版本
No branches or pull requests
我在尝试 npm install 的时候出现了这个。 是因为 node 版本还是其他原因吗?
希望大佬能够解答
The text was updated successfully, but these errors were encountered: