You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using frida-il2cpp-bridge, I encounter issues with code completion, intellisense, and errors related to missing member properties (Property does not exist on type {}).
Problem Overview
Upon integrating frida-il2cpp-bridge into my project via npm, I noticed that it behaves differently compared to other libraries. Specifically, I'm facing issues with code completion and intellisense within Visual Studio Code. Whenever I attempt to access certain members or properties, I receive errors indicating that these properties do not exist on the type.
Screen Shoot
Working 100% for other Libraries
this is working 100% for Frida's JS API within same project , same .ts file. Code Intellisense is working 100% for libraries excluding frida-il2cpp-bridge
Expected Behavior
I expected frida-il2cpp-bridge to provide complete code hints, intellisense, and proper property recognition within my development environment, similar to other libraries I've used. However, this behavior seems to be absent or inconsistent, resulting in errors during development.
Installation
npm -i frida-il2cpp-bridge
Additional Information
Code completion and Intellisense is working for other libraries.
I've ensured that the library was installed correctly and is up to date.
I am using TypeScript file for coding my stuff, (.ts)
I've done the setup as described but nothing works for me. after troubleshooting of 2 days I reported this issue on GitHub repo. I described this issue in Frida's Telegram Channel but nobody had any idea about the solution.
Recently I noticed that when I use .JS file to code instead of .TS file the VS Code never show any error but the code intellisense and auto completion still remains disabled for this library, this is just like ignoring the errors - not helpful
I've done the setup as described but nothing works for me. after troubleshooting of 2 days I reported this issue on GitHub repo. I described this issue in Frida's Telegram Channel but nobody had any idea about the solution.
Recently I noticed that when I use .JS file to code instead of .TS file the VS Code never show any error but the code intellisense and auto completion still remains disabled for this library, this is just like ignoring the errors - not helpful
Hardly relevant, but I found a solution.
You need to delete the file tsconfig.json, and reinitialize the project through the terminal with the command tsc -init
After that autocompletion and highlighting will work correctly.
When using frida-il2cpp-bridge, I encounter issues with code completion, intellisense, and errors related to missing member properties (Property does not exist on type {}).
Problem Overview
Upon integrating frida-il2cpp-bridge into my project via npm, I noticed that it behaves differently compared to other libraries. Specifically, I'm facing issues with code completion and intellisense within Visual Studio Code. Whenever I attempt to access certain members or properties, I receive errors indicating that these properties do not exist on the type.
Screen Shoot
Working 100% for other Libraries
this is working 100% for Frida's JS API within same project , same .ts file. Code Intellisense is working 100% for libraries excluding frida-il2cpp-bridge
Expected Behavior
I expected frida-il2cpp-bridge to provide complete code hints, intellisense, and proper property recognition within my development environment, similar to other libraries I've used. However, this behavior seems to be absent or inconsistent, resulting in errors during development.
Installation
Additional Information
Code completion and Intellisense is working for other libraries.
I've ensured that the library was installed correctly and is up to date.
I am using TypeScript file for coding my stuff, (.ts)
Project's Packag.json file
Project's tsconfig.json file:
Environment Details:
The text was updated successfully, but these errors were encountered: