Skip to content

Debugging documentation doesn't address virtual host name mapping #2157

Open
@jaredkrinke

Description

@jaredkrinke

Link to the documentation page:
https://docs.microsoft.com/en-us/microsoft-edge/webview2/how-to/debug-visual-studio-code

Description of the issue:

The example launch.json sets the URL to a "file" protocol URL, but the WebView2 "getting started" docs suggest using SetVirtualHostNameToFolderMapping to map HTTP URLs to local folders.

How do you tell VS Code that "https://example.com/" is actually loaded from the file system, e.g. for loading source maps?

When I attempt to debug my WebView2 app which has a script mapped to "https://example.com/index.js", VS Code actually tries to request the source map from "https://example.com/index.js.map" instead of reading from my local file system, which makes me think that additional flags in the launch.json file are required.

Given that virtual host name mapping seems to be recommended, the debugging instructions should cover how to debug mapped files.

AB#41242137

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions