[docs] Debug with jetbrains rust rover including front end

[delebash]

I followed the docs here https://v2.tauri.app/develop/debug/rustrover/ but this does not include the front end for break points.

I am using the @tauri-apps/plugin-http' to fetch some data. When I debug according to the docs above none of my javascript breakpoints are hit but the fetch code runs fine in the tauri app. If I add a normal javascript debugging session for the default url of http://localhost:1420/ it opens a web page and my javascript break points are hit. However, because it is in the context of a webpage and not a tauri app the fetch code throws an invoke error.

How can I debug the javascript code that also invokes a call to rust with rustrover. TY

[bling-yshs]

I've also had this problem for a while, and I finally solved it today. According to this document: Make Tauri frontend side better debugging experience as a regular web app, you can debug your Tauri frontend code in a JetBrains IDE by following these steps:

1. Add a Cargo configuration:

   • Command: run --no-default-features
   • Working directory: D:/xxx/src-tauri (Replace D:/xxx with your actual project path)
   • Environment variables: WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS=--remote-debugging-port=12345
   • Save the configuration. (Note: This environment variable is very important and must be added.)

2. Add an npm configuration:

   • Command: run
   • Script: dev
   • Save the configuration.

3. Add an "Attach to Node.js/Chrome" configuration:

   • Host: localhost
   • Port: 12345 (This corresponds to the --remote-debugging-port=12345 from step 1.)
   • Save the configuration.

4. Execution Order:

   • First, run or debug run the Cargo configuration from step 1.
   • Then, debug run the npm configuration from step 2.
   • Finally, debug run the "Attach to Node.js/Chrome" configuration from step 3.

5. Set Breakpoints: Add breakpoints in your frontend code.

6. Debug: The breakpoints should now be triggered normally. Finished.

[r0yx1e]

On macOS, using wkwebview, so cannot open remote-debugging-port. Is there any other way?