Skip to content
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

How to debug webview code? #18

Closed
hellozyemlya opened this issue Oct 24, 2024 · 4 comments
Closed

How to debug webview code? #18

hellozyemlya opened this issue Oct 24, 2024 · 4 comments

Comments

@hellozyemlya
Copy link

hellozyemlya commented Oct 24, 2024

First of all, many thanks for extension, it works as described and very well.

Question is - how I can connect debugger to resulting iframe and actually debug webview typescript code with build in vs code debugger or any other debugger?
Thanks in advance.

tomgao365 added a commit that referenced this issue Oct 25, 2024
@tomgao365
Copy link
Member

Hi @hellozyemlya , now you can try v3.10+.
During development, support standalone development tool applications for react and vue, enabled by default.

  • react: inject <script src="http://localhost:8097"></script>, support react-devtools
  • vue: inject <script src="http://localhost:8098"></script>, support vue-devtools

@hellozyemlya
Copy link
Author

@tomgao365 wow, that is cool, many thanks. Not exactly what I wanted\asked for, but will be helpful(I really struggled a lot once, where failed with slow react rendering... it forced me to mock out all vs code api and run webview directly in browser).

But is there some vite plugin or other way that will expose port connectable\attachable via regular debugger, like vs code one build in, or jetbrains webstorm?

Regardless, having react-devtools is super cool!

@tomgao365
Copy link
Member

@hellozyemlya 😂 Sorry, I haven't studied this type of debugger. You can only see if there are other Vite plugins that support it.

@hellozyemlya
Copy link
Author

@tomgao365 no problems. I realized that this is probably a question for VS Code team itself. I guess you can close this issue if you want.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants