Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

VSCode Launch.JSON

See original GitHub issue

Is your feature request related to a problem? Please describe.
It would be awesome if the direflow CLI provided a launch.json to build and debug direflow WebComponents out of the box.

Describe the solution you’d like
Ideally the CLI would provide a launch.json configuration that allows launching and debugging + attaching to a direflow project.

Describe alternatives you’ve considered
A clear and concise description of any alternative solutions or features you’ve considered.

Additional context

https://code.visualstudio.com/docs/editor/debugging

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

say25commented, Aug 17, 2020

I got this working with the below launch.json. I intentionally have it not open a browser in the yarn start step to avoid having two instance going at the same time

{
  // 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": [
    {
      "command": "yarn start:no-browser",
      "name": "Run yarn start",
      "request": "launch",
      "type": "node-terminal",
      "presentation": {
        "hidden": true,
        "group": "",
        "order": 2
      }
    },
    {
      "type": "pwa-chrome",
      "request": "launch",
      "name": "Launch Chrome against localhost",
      "url": "http://localhost:3000",
      "webRoot": "${workspaceFolder}/src",
      "skipFiles": ["${workspaceFolder}/node_modules/"],
      "presentation": {
        "hidden": true,
        "group": "",
        "order": 1
      }
    },
    {
      "type": "pwa-msedge",
      "request": "launch",
      "name": "Launch Edge against localhost",
      "url": "http://localhost:3000",
      "webRoot": "${workspaceFolder}/src",
      "skipFiles": ["${workspaceFolder}/node_modules/"],
      "presentation": {
        "hidden": true,
        "group": "",
        "order": 1
      }
    }
  ],
  "compounds": [
    {
      "name": "Chrome Launch and Debug",
      "configurations": ["Run yarn start", "Launch Chrome against localhost"],
      "stopAll": true
    },
    {
      "name": "Edge Launch and Debug",
      "configurations": ["Run yarn start", "Launch Edge against localhost"],
      "stopAll": true
    }
  ]
}

0reactions

SimonHoibergcommented, Sep 30, 2020

We’re gonna carry on with this feature here.

Top Results From Across the Web

Debugging in Visual Studio Code

VS Code keeps debugging configuration information in a launch.json file located in a .vscode folder in your workspace (project root folder) or in...

Configure launch.json for C/C++ debugging in Visual Studio ...

Visual Studio Code generates a launch.json (under a .vscode folder in your project) with almost all of the required information. To get started...

Visual Studio Code documentation search

Run and Debug Java in Visual Studio Code. The launch.json file is located in a .vscode folder in your workspace (project root folder)....

Introduction to Debugging in Visual Studio Code

In this tutorial, we will show you how to run and debug a program in VS Code. We'll take a tour of the...

Debug Node.js Apps using Visual Studio Code

Debugging configurations are stored in a launch.json file located in your workspace's .vscode folder. An introduction into the creation and use of debugging ......