#Debug in VS Code and Yew frontend

2 messages · Page 1 of 1 (latest)

obsidian chasm
#

Hi there. I'm having a problem debugging the project with the Yew front-end. I keep getting panics on application start about using wasm-bindgen on non-wasm target. Is there any way to overcome these issues? Also, the debugger does not see the "problemMatchers" declaration, even though it exists.

launch.json:

#
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
      {
        "type": "lldb",
        "request": "launch",
        "name": "Tauri Development Debug",
        "cargo": {
          "args": [
            "build",
            "--manifest-path=./src-tauri/Cargo.toml",
            // "--manifest-path=./Cargo.toml",
            "--no-default-features"
          ]
        },
        // task for the `beforeDevCommand` if used, must be configured in `.vscode/tasks.json`
        "preLaunchTask": "ui:dev"
      },
      {
        "type": "lldb",
        "request": "launch",
        "name": "Tauri Production Debug",
        "cargo": {
          "args": [
            "build", 
            "--release", 
            "--manifest-path=./src-tauri/Cargo.toml"
            // "--manifest-path=./Cargo.toml"
          ]
        },
        // task for the `beforeBuildCommand` if used, must be configured in `.vscode/tasks.json`
        "preLaunchTask": "ui:build"
      }
    ]
  }