Skip to content

AddConfigurations does not respect { on the same line as [ #22624

@nicolehaugen

Description

@nicolehaugen
  • VSCode Version: 1.11.0-insider
  • OS Version: Win 10

I can't quite figure out exactly what seems to cause this, but a common factor seems to be when the launch.json file is hand-edited as mentioned in the repro steps. Once VS code gets into a state where the Node.js specific debug config options are displayed, I can't figure out how to get them back - the only way I have found is to delete the launch.json file and start over which obviously isn't ideal.

Steps to Reproduce:

  1. In VS Code, clone the following node.js project: https://github.com/scotch-io/node-todo
  2. Open the above project, click the debug button in the left hand pane, and then in the debug configuration drop-down menu, choose to "Add configuration" (note that at this point, you shouldn't have any configurations created).
  3. From the configuration popup menu, notice that you are presented with a list of common Node.js configurations - select the "Node.JS: Launch Program" configuration.
  4. In the first configuration option, change the "program" value to "${workspaceRoot}/server.js" - don't change anything else in the file and then save.
  5. Open the debug configuration drop-down menu again and choose "Add configuration".

This time, when the configuration popup menu is displayed, all of the Node.js configuration options are missing. Refer to the first attached screen shot shows the actual list; the second screenshot shows what should be displayed instead.

actual
expected

Metadata

Metadata

Assignees

Labels

bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions