Skip to content

Guidance for debugging Edge Addons (aka Chrome Extensions) #3368

@JustinGrote

Description

@JustinGrote

Is your feature request related to a problem? Please describe.

When I start a debug launch, breakpoints don't bind for extensions even after loading them unpacked

Describe the solution you'd like:

A section in the docs or a sample in the repo that clearly explains how to configure the Edge extension with a launch config that can breakpoint an Addon, so I can set a breakpoint in vscode, do the action in the browser such as open the extension popup, and have it hit that breakpoint.

Describe alternatives you've considered:

Just running in devtools or debug mode and connecting via port

Additional context:

This works automatically in builtin JS Debugger with this config:

		{
			"type": "chrome",
			"request": "launch",
			"name": "Chrome Extension Debug",
			"url": "https://portal.azure.com",
			"runtimeArgs": ["--load-extension=${workspaceFolder}/dist"]
		}

So why doesn't it work when I change the type to "edge"?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions