Skip to content
New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom

launch.json generation #12460

Closed
1 task done
isidorn opened this issue Sep 22, 2016 · 2 comments
Closed
1 task done

launch.json generation #12460

isidorn opened this issue Sep 22, 2016 · 2 comments
Assignees
@seanmcbreen
Labels
testplan-item
Milestone
September 2016

Comments

@isidorn
Copy link
Contributor

isidorn commented Sep 22, 2016 •
edited by egamma
Loading

Complexity: 2

We have changed the way how we get the content for the initial 'launch.json'. More details #9061.
Have a workspace with no 'launch.json' file and verify:

  • A proper 'launch.json' gets generated for the following debug types: node, extension host, go...
  • For node debugging the content of the 'package.json' is read and the generated 'program' attribute in 'launch.json' points to the one referenced there (example: use vscode-smoketest-express workspace)
@isidorn isidorn added this to the September 2016 milestone Sep 22, 2016
@kieferrm kieferrm mentioned this issue Sep 22, 2016
Closed
@isidorn isidorn mentioned this issue Sep 26, 2016
Closed
3 tasks
@chrmarti
Copy link
Collaborator

Related #8937

@egamma egamma closed this as completed Sep 29, 2016
@Skamau
Copy link

Skamau commented Mar 15, 2017

screenshot 2017-03-15 16 24 24
this is not working for me..please help

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Assignees

@seanmcbreen seanmcbreen

Labels
testplan-item
Projects
None yet
Milestone
September 2016
Development

No branches or pull requests
5 participants
@egamma @seanmcbreen @isidorn @chrmarti @Skamau