KEMBAR78
Launch Config Parity · Issue #26 · microsoft/vscode-js-debug · GitHub
Skip to content

Launch Config Parity #26

@connor4312

Description

@connor4312

New Options

The following new options are tracked for support:

  • logging -- new logging object that improves granularity
  • nodeFilter
  • baseURL -- (reconcile with path mappings?)

Additionally, vscode-pwa supports booting and debugging a server and client in a single launch config. It would make sense to preserve that behavior. Therefore, the chrome launch action config can have an additional property server that contains the Node launch config.

{
  "type": "pwa-chrome",
  "request": "launch",
  "name": "Web page 2",
  "url": "http://localhost:5002",
  "server": {
    "program": "${workspaceFolder}/main.js"
  }
}

Existing Options

We want to make vscode-pwa match and reach parity with the existing launch config options. This tracks that works.

node: launch

node: attach

chrome: launch

chrome: attach

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature-requestRequest for new features or functionality

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions