v2.1.3

• Error handling for invalid messages from Chrome, to avoid crashing - #274
• Fix potential issue with sourcemap path handling on Windows

v2.1.2

• Revert an earlier change to the filtering logic, which only worked for vscode 1.7+, and caused some objects to not be expandable - #273

v2.1.0

• Object previews - see the first several properties of an object or array inline, without having to expand it - Microsoft/vscode-chrome-debug-core#120
• Fix debugging with file:/// paths on windows - #264

v2.0.0

• New feature - set "smartStep": true to automatically step over code that doesn't have a sourcemapping - Microsoft/vscode-chrome-debug-core#34
• Switch to new log API to fix #245
• Invalid watches say "not available" instead of showing an error - Microsoft/vscode-node-debug2#31
• Completions are shown when typing in the console - Microsoft/vscode-chrome-debug-core#87
• Variables tree is not jarringly redrawn between steps - Microsoft/vscode-node-debug2#30
• Target userAgent is logged under 'diagnosticLogging'
• And a few large non-feature engineering changs

v1.2.1

• Disable caching downloaded sourcemaps, hoping to fix #247

v1.2.0

1.2.0

• Change the way that sourcemaps are downloaded, hoping to fix #251
• Fix breakpoints being moved around after refreshing the page - #250
• Fix global eval sometimes failing, and incorrect error handling - #244
• Fix error with sourcemaps for eval scripts - #256

v1.1.0

• Changed the way that targets are queried for, hoping to fix #237
• Enable breakpoints for fsharp - #243 - Thanks @octref
• Fix -core links in changelog - #239 - Thanks @marvinhagemeister

v1.0.0

• Evaluate getters in the variables pane - Microsoft/vscode-chrome-debug-core#77
• Paging chunks of large arrays - Microsoft/vscode-chrome-debug-core#4
• Show Map/Set members - Microsoft/vscode-chrome-debug-core#31
• Show inlined sources when the source can't be resolved to a file on disk - Microsoft/vscode-chrome-debug-core#85
• Hover on breakpoints to see error messages when breakpoints don't bind - Microsoft/vscode-chrome-debug-core#38
• Editing variable values - Microsoft/vscode-chrome-debug-core#58
• Conditional breakpoints - Microsoft/vscode-chrome-debug-core#10

v0.5.2

• Fix console messages in Chrome 54+ (Canary, at the moment) - #208

v0.5.1

• Add better error message for attaching when chrome devtools is attached - #203
• Fix array sorting - microsoft/vscode-chrome-debug-core#62
• Make eval scripts properly highlighted as javascript - microsoft/vscode-chrome-debug-core#59
• Launch Chrome when it's installed to AppData - microsoft/vscode-chrome-debug-core#50
• Handling for targets that have some devtool already attached - #203, #204
• Log 1-indexed numbers in sourcemap messages - #55