v3.1.1

• Fix "extension.chrome-debug.startSession not found" error due to bad publish

v3.1.0

• Implement column breakpoints (with shift+F9) for recent Chrome versions - Microsoft/vscode-chrome-debug-core#144
• Show a quickpick with available tabs when there are multiple - #280
• Add webpack:///./~/ sourcemap mapping by default - #401
• Add webpack:///src/* sourcemap mapping for create-react-app by default - #315
• Show exception widget for breaking on promise rejection - Microsoft/vscode#21929
• Completely fix showing empty property names as "" - Microsoft/vscode#24143
• Fix "Open or close parenthesis in file path prevents debugger from discovering the target" - #373
• Remove "unimplemented console API" warning
• Specify languages for creating a launch config when none is set up - #334

v3.0.1

• Fix "Windows - Electron app fails to start after upgrading to 3.0.0" #407
  • On Windows, the code to prevent Chrome from closing when opening Chrome Devtools #116 is now not enabled when specifying a runtimeExecutable, until I find a better solution.

v3.0.0

• Enable userDataDir by default - #210
• Keep Chrome open when launching chrome devtools (now also on Windows) - #116
• Error while debugging: Unable to open 'undefined': File not found (/undefined) - Microsoft/vscode-chrome-debug-core#189
• Show empty property names as "" - Microsoft/vscode#24143

v2.7.3

• Fix missing variables and error "Cannot read property 'length' of undefined" - Microsoft/vscode-chrome-debug-core#195
• Fix sourcemapping issue when throwing non-Error
• Fix exception messages in the console missing a trailing newline
• Exception sourcemapping should also map non-sourcemapped scripts to file on disk

v2.7.2

• Fix "pathMapping key must end in '/'" - thanks to @mlewand for the PR! - #393
• Add "Toggle skipping this file" context menu option to callstack - Microsoft/vscode-chrome-debug-core#172
• Document "showAsyncStacks" launch config option (VS Code 1.11 recommended)
• Don't repeat exception description in exception info widget - Microsoft/vscode-chrome-debug-core#192
• Fix error in async stacks when no sourcemaps are present

v2.7.1

• Support source mapping of stack traces in the Debug Console - thanks to nojvek for the PR! - Microsoft/vscode-chrome-debug-core#190
• Show error callstack in new Exception widget when pausing on an exception (sourcemapped, thanks to the above)
• Fix BPs sometimes removed when editing while debugging - Microsoft/vscode#22492
• Fix some errors when stepping quickly - Microsoft/vscode#22855
• Show "Chrome" instead of "Thread 1" as thread name when debugging multiple things at once
• Fix crash when debugging with async callstacks and sourcemaps disabled

v2.7.0

• Implement disableNetworkCache option - #358
• If you are using VS Code 1.11, set the undocumented property showAyncStacks to see async callstacks.
• Implement urlFilter to give 'launch' configs a way to select which page to attach to, e.g. for Electron apps with multiple BrowserWindows - #382
• Nicer error messages when a source map fails to parse - thanks to nojvek for the PR! - Microsoft/vscode-chrome-debug-core#188
• Fix code that prevents the extension from incorrectly attaching to a Chrome extension
• Fix crash when 'url' is not specified in an 'attach'-type config

v2.6.0

• When opening Chrome Devtools, Chrome will no longer crash. The debugger will still detach (only one debugger can be attached at a time) but you should be able to switch back and forth.
• The timeout when launching or attaching to Chrome is now configurable. It's 10s by default. - #346
• Fix setting BPs in source that's inlined in a sourcemap - Microsoft/vscode-chrome-debug-core#180
• Fix breakpoints shifting in some situations where they shouldn't, when Chrome returns a BP location that can't be sourcemapped - Microsoft-node-debug2#90
• Add a pause reason for promise rejection - Microsoft-node-debug2#46
• Show exception text in the new exception widget in VS Code 1.10 - Microsoft/vscode-chrome-debug-core#181
• diagnosticLogging and verboseDiagnosticLogging are now deprecated in favor of the trace option. "trace": true will write all logs to a file, and write the path to the file in the debug console. "trace": "verbose" will write all logs to the debug console, and to the file.

v2.5.5

• Fix "Cannot find context with specified id" error spam - #264