Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow runtimeExecutable to be set globally #836

Closed
raulfpl opened this issue Oct 24, 2019 · 2 comments
Closed

Allow runtimeExecutable to be set globally #836

raulfpl opened this issue Oct 24, 2019 · 2 comments
Assignees
Labels
feature-request Request for new features or functionality verification-needed Verification of issue is requested verified Verification succeeded
Milestone

Comments

@raulfpl
Copy link

raulfpl commented Oct 24, 2019

There should be a way to set the runtimeExecutable as a user config for the extension. That way you could set it up once instead of doing it for every new project, in case you don't have Chrome installed to one of the default paths.

@connor4312 connor4312 transferred this issue from microsoft/vscode-chrome-debug Nov 3, 2020
@connor4312 connor4312 assigned connor4312 and unassigned roblourens Nov 3, 2020
@connor4312 connor4312 added the feature-request Request for new features or functionality label Nov 3, 2020
@connor4312 connor4312 added this to the November 2020 milestone Nov 3, 2020
@connor4312 connor4312 added the verification-needed Verification of issue is requested label Nov 3, 2020
@connor4312
Copy link
Member

This can now be done via the debug.javascript.defaultRuntimeExecutable setting. Note that this happens at config resolution time, so for the moment only works with pwa- prefixed configs (e.g. if you have a launch type named node, then rename it to pwa-node)

@jtsom
Copy link

jtsom commented Nov 5, 2020

Just FYI... I added this

    "debug.javascript.defaultRuntimeExecutable": {
      "pwa-node": "node",
      "pwa-chrome": "dev"
    }

to my settings and that launched my Dev Chrome BlazorWasm application just fine.

Thanks!

digeff pushed a commit that referenced this issue Nov 9, 2020
@roblourens roblourens added the verified Verification succeeded label Dec 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality verification-needed Verification of issue is requested verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants