-
Notifications
You must be signed in to change notification settings - Fork 183
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
_agent.js NOT like a normal js file #24
Comments
Hi, The new frida-compile outputs a Frida-specific container format for multiple ESMs in a single .js, and that's what you're seeing. Check out the new frida-tools -- there is now a frida-compile tool there and the REPL supports loading .ts files through Cheers! |
Can I use |
I have the same issue here |
+1 |
@andreafioraldi the problem is the line break on Windows. Mine solved by suppplying with (filename).open('r', encoding='utf8', newline='\n') as fp:
return fp.read() |
你好请问有解决吗 |
Dude, you are writing just under the answer. |
Hi. I checkout the latest version (c709844). When i run
npm run build
(frida-compile agent/index.ts -o _agent.js -c
) , the output file_agent.js
include emoji, and it not like a normal js file. I also trynpm run watch
(frida-compile agent/index.ts -o _agent.js -w
)I try to find the reason. I found this at
frida-compile
, and understand the output is normal.But i don't know why
_agnet.js
work in frida. Maybe it only work in Frida? Or new features of the js engine? Any helpful info?I also try to find the parameters in
frida-compile
where I could get a normal javascript output file, but nothing there. What i miss?Thanks.
The text was updated successfully, but these errors were encountered: