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
Deilan opened this issue
Jan 25, 2018
· 4 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
******** Unhandled error in debug adapter - Unhandled promise rejection: TypeError: Cannot read property 'line' of null
at ChromeDebugAdapter.<anonymous> (C:\Users\Deilan\.vscode\extensions\msjsdiag.debugger-for-chrome-4.0.0\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:575:61)
at Generator.next (<anonymous>)
at C:\Users\Deilan\.vscode\extensions\msjsdiag.debugger-for-chrome-4.0.0\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:10:71
at Promise (<anonymous>)
at __awaiter (C:\Users\Deilan\.vscode\extensions\msjsdiag.debugger-for-chrome-4.0.0\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:6:12)
at details.forEach (C:\Users\Deilan\.vscode\extensions\msjsdiag.debugger-for-chrome-4.0.0\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:566:48)
at Array.forEach (native)
at ChromeDebugAdapter.<anonymous> (C:\Users\Deilan\.vscode\extensions\msjsdiag.debugger-for-chrome-4.0.0\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:566:25)
at Generator.next (<anonymous>)
at fulfilled (C:\Users\Deilan\.vscode\extensions\msjsdiag.debugger-for-chrome-4.0.0\node_modules\vscode-chrome-debug-core\out\src\chrome\chromeDebugAdapter.js:7:58)
Steps to Reproduce:
Angular CLI 1.6.5 project
npm start
Launch debugger
The text was updated successfully, but these errors were encountered:
Thanks for the sample project. It's caused by a script in the sourcemap with a weird name - ["/Users/roblou/Documents/vscode-issue-42162/node_modules/moment/locale ^\\.\\/.*$"]. Looking at your build, I have no idea where the pattern at the end comes from. But it exposes a slight problem with how source paths are handled.
roblourens
added
bug
Issue identified by VS Code Team member as probable bug
and removed
info-needed
Issue requires more information from poster
labels
Jan 28, 2018
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
Debug Console's output:
Steps to Reproduce:
npm start
The text was updated successfully, but these errors were encountered: