You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
johan-gorter opened this issue
Mar 3, 2016
· 2 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
We had some team members who could not debug mocha unit-tests and others who could. We tracked the problem down to the path which contained spaces (in our case c:\development next\frontend) . This is probably also the cause of issues #3144 and #3659.
This issue has appeared in the last month, before that, we did not have problems with spaces in the path. We suspect that something is wrong with reading the sourcemaps.
The text was updated successfully, but these errors were encountered:
isidorn
added
the
debug
Debug viewlet, configurations, breakpoints, adapter issues
label
Mar 3, 2016
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
We had some team members who could not debug mocha unit-tests and others who could. We tracked the problem down to the path which contained spaces (in our case c:\development next\frontend) . This is probably also the cause of issues #3144 and #3659.
This issue has appeared in the last month, before that, we did not have problems with spaces in the path. We suspect that something is wrong with reading the sourcemaps.
The text was updated successfully, but these errors were encountered: