34 KiB
34 KiB
Note: Active development for Chrome debugging in VS Code is happening in http://github.com/microsoft/vscode-js-debug. The vscode-chrome-debug repo will soon be considered deprecated.
4.12.9 - 4.12.7
- Making
debug.javascript.usePreview
the default
4.12.6
- Respect the
debug.javascript.usePreview
setting
4.12.5
- Don't respect the
"debug.chrome.useV3"
setting in a remote window, because that debugger doesn't support the remote scenario yet
4.12.4
- Register "useV3" setting officially
4.12.3
- Fix error when using restartFrame on Electron - Microsoft/vscode#86411
4.12.2
- Fix error when setting value on property - Microsoft/vscode-node-debug2#250
4.12.1
- Hide
[[StableObjectId]]
variable - Microsoft/vscode-chrome-debug-core#396 - Hide
breakpointLocations
errors from console
4.12.0
- Show all possible breakpoint locations - #934
4.11.7
- Support clearing the current color in console.log color format args - microsoft/vscode#76550
4.11.5
- Fix remote debugging issue - #867
4.11.4
- Fix debugging in a remote window with chrome-debug as a UI extension - #832
4.11.3
- Fix frames labeled as
smartStep
when they shouldn't be - Microsoft/vscode#68127 - Fix slow attach when files don't exist on disk - Microsoft/vscode#69118
4.11.2
- Fix disabling smartStep - Microsoft/vscode#68464
- Fix smartStep frames sometimes not grayed out - Microsoft/vscode#65025
- Various minor bug fixes
4.11.1
- Enable
smartStep
by default - Microsoft/vscode#62965 - Enable
showAsyncStacks
by default, finally - Fix some frames incorrectly labelled as "skipped by smartStep"
4.11.0
- Support %c styling in console.log - thanks to @rdegelo for PR #367 and PR #374.
- Fixes for breakOnLoad edge cases
4.10.2
- Only show callstack context menu on stack frames - Microsoft/vscode#19180
- Fix missing breakpoints on first line of script in Chrome 69 - Microsoft/vscode-chrome-debug-core#352
4.10.1
- Add the
targetTypes
config parameter to allow attaching to targets other thanpage
. Note that this extension doesn't officially support debugging other types of targets, but this may enable some advanced debugging scenarios. Thanks to @stristr for the PR! - Microsoft/vscode-chrome-debug-core#350 and #727
4.10.0
- Enable
disableNetworkCache
by default - #725 - Fix for runtimes that don't support the
Log
domain - Microsoft/vscode#58053
4.9.1
- Support
console.clear()
- Show errors from Chrome itself, e.g. 404s and other network errors
4.9.0
- Support new "Loaded Scripts" view in VS Code 1.27 - Microsoft/vscode#55462
- Use less memory when running for a long time with lots of scripts - Microsoft/vscode#53535
4.8.2
- Fix error "Cannot read property 'startsWith' of undefined"
4.8.1
- Allow setting env vars to "null" like when debugging node - #706
- Fix rare issue killing Chrome on Windows - PR #703
- Allow URI-encoded inline source maps - thanks to @Pokute for the PR! - Microsoft/vscode-chrome-debug-core#343
4.8.0
- Change
smartStep
to only skip through unmapped lines in files with sourcemappings, not files that don't have sourcemappings. You should useskipFiles
to skip files that don't have sourcemappings (like node_modules) - Don't crash if Chrome sends a scope with invalid locations - Microsoft/vscode-chrome-debug-core#333
4.7.0
- Don't blink the Chrome pause overlay when starting with breakOnLoad enabled - #689
- Fix debug adapter error when an error is thrown from native code - Microsoft/vscode-chrome-debug-core#334
- Fix logging empty strings - Microsoft/vscode#52028
- Fix breaking in random script with breakOnLoad enabled - #686
- Fix a
pathMapping
case that broke after v4.5.0 #684
4.6.0
- Enable breakOnLoad by default 🎉 - #594
- Fix skipFiles in some cases when sourcemappings don't cover the full document, like in webpack - #667
- Fix downloading sourcemaps when offline - #638
- Fix an incorrect sourceMappingUrl case - #653
- Fix global completions in Debug Console when not at a breakpoint - Microsoft/vscode-chrome-debug-core#331
4.5.0
- Fix
pathMapping
differences withwebRoot
- #643
4.4.1
- 4.4.0 was a bad publish. Republished to fix #655
4.4.0
- Allow enabling auto
userDataDir
when runtimeExecutable is set - #641 - Show correct source locations for log messages from logpoints - Microsoft/vscode#47274
- Display objects in logpoint messages using interactive object tree view - Microsoft/vscode#47275
- Fix incorrectly formatted
.scripts
entries - Remove left behind
targetTypes
attach config prop - More localized strings
- A variety of smaller fixes and tweaks
4.3.0
- Enable "log points", requires VS Code 1.22 - Microsoft/vscode#45128
- Workaround for
"'Browser.getVersion' wasn't found"
issue - #633
4.2.2
- Fix another breakpoints case related to Microsoft/vscode#45657
- Fix NPE when toggling skip on files that are only in the stack after a label or async frame
- Fix "start without debugging" navigation - Microsoft/vscode-chrome-debug#620
4.2.1
- Fix Windows issue with breakpoints not binding if they were set before launch - Microsoft/vscode#45657
- Work around issue where hover shows wrong 'this' - Microsoft/vscode#44785
- Fix Chrome session restore prompt showing on every start - thanks to @aj-r for the PR! - PR #606
4.2.0
- Use more precise extension activation events to prevent unneeded activation
- Apply sourceMapPathOverrides in order of longest->shortest, instead of key order within the object - Microsoft/vscode-chrome-debug-core#297
- Make sourceMapPathOverrides default values in package.json match the defaults applied in code - #581
- Add "Toggle Smart Step" command - Microsoft/vscode-chrome-debug-core#298
- Fix error when setting BP in scripts with certain weird sourcemap names - Microsoft/vscode#42162
- Fix various breakOnLoad-related issues - PR Microsoft/vscode-chrome-debug-core#283, PR Microsoft/vscode-chrome-debug-core#285 and others
4.1.0
- Implement "step into async code". "step in" on
setTimeout
will now step into the body of the setTimeout if no other breakpoints are hit first. Requires Chrome 65 - Microsoft/vscode-chrome-debug-core#266 - Show exception scope for top frame only - Microsoft/vscode-chrome-debug-core#233
- Fix regex character handling in the left side of
sourceMapPathOverrides
- thanks to @msafi for the PR! - PR Microsoft/vscode-chrome-debug-core#261 - Fix errors showing up in some breakpoint scenarios - thanks to @obastemur for the PRs! - PR Microsoft/vscode#263 and PR Microsoft/vscode-chrome-debug-core#265
- Parse sourcemaps more lazily, to improve startup performance
- Fix
.*
pattern inskipFiles
(literal.
followed by wildcard) - Microsoft/vscode-chrome-debug-core#268 - Fix broken "Toggle skipping this file" command (in Insiders) - Microsoft/vscode#41945
- Fix race condition in handling skipFiles in some sourcemapped files - Microsoft/vscode-chrome-debug-core#266
4.0.0
- Implement the
breakOnLoad
launch config option to hit breakpoints in code that runs immediately when the page logs - PR #513 and PR Microsoft/vscode-chrome-debug-core#241 - Most strings (error messages, launch config property descriptions, etc) are now translated on Transifex
- Resolve
webRoot
variables on the left side ofsourceMapPathOverrides
mappings, not just the right side. Thanks Amit Mittal for the PR! - PR #543 - Set focus in
webRoot
after using a launch config snippet - #539 - Fix error/log messages out of order due to async handling - Microsoft/vscode#37770
3.5.0
- Support debug console colorization for eval results - Microsoft/vscode#35324
- Fix rare NPE when running in noDebug mode - Microsoft/vscode-node-debug2#149
- Remove deprecated startSessionCommand API - #517
3.4.0
- Show locations for exception messages in the Debug Console
- Fix unmapped names on some stack frames, thanks to @digeff for the PR! - Microsoft/vscode-chrome-debug-core#246
- Exclude some files from the package to make it slightly smaller - thanks to @torn4dom4n for the PR! - Microsoft/vscode-chrome-debug-core#248
- Terminate properly after running in noDebug mode - Microsoft/vscode#36235
- Fix skipping some promise rejections improperly - Microsoft/vscode-chrome-debug-core#250
- Add
env
andcwd
launch config options, thanks to @jpap for the PR! - Microsoft/vscode-chrome-debug#520
3.3.1
- (In VS Code 1.17), show the source location of log statements and exceptions in the debug console - Microsoft/vscode#34626
- Fix error messages that can appear when detaching from Chrome - Microsoft/vscode#34615
3.3.0
- Show whether paused exception was caught or uncaught - #234
- Fix issue where 'attach' configs ignores 'timeout' and fails immediately instead of retrying - #501
- Look up runtimeExecutable scripts with correct extensions for Windows - #448
3.2.1
- Fix pause overlay on Chrome window - #486
3.2.0
- Support 'Command Line API' in the console - commands like
$_
and$(selector)
will now work. - Wait for sourcemaps to finish loading before resolving sourcemaps in stack traces.
- Fix error from triggering 'reload' before attaching to Chrome - #484
3.1.8
- Fix for old runtimes that don't support setAsyncCallStackDepth - Microsoft/vscode-chrome-debug-core#226
- Download sourcemaps referenced with file:/// properly - Microsoft/vscode-chrome-debug-core#205
- Fix errors when stepping too quickly - Microsoft/vscode#27696
- Fix some values not formatted correctly in the debug console - Microsoft/vscode#32064
3.1.7
- Fix hover on variables defined in async functions using TS transpilation - Microsoft/vscode#31469
- Decrease extension package size
3.1.6
- Support
console.dir
and other missingconsole
APIs - Microsoft/vscode#29602 - Resolve longer
pathMapping
mappings before resolving shorter ones - #444
3.1.5
- Fix evaluating object literals in the console - Microsoft/vscode-node-debug2#104
- Fix error callstacks in console sometimes not being sourcemapped - Microsoft/vscode-chrome-debug-core#212
3.1.4
- Fix breakpoints not binding in apps built with Angular 1.1.1 (or any other app with a particular webpack config) - Microsoft/vscode#28730
- Restore ability to create a launch.json with the default configs when pressing F5, and one is not already present.
3.1.3
- Fix longstanding sourcemap location mapping error - #112
- Add existing default values to the
sourceMapPathOverrides
launch config setting
3.1.2
- Fix first frame appearing twice (in VS Code 1.13) and fix callstack paging - Microsoft/vscode#25594
- Enhance path matching by accepting partial paths in
pathMapping
- thanks to llgcode for the PR! - Microsoft/vscode-chrome-debug-core#202
3.1.1
- Fix "extension.chrome-debug.startSession not found" error due to bad publish
3.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
3.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.
3.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
2.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
2.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
2.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
2.7.0
- Implement
disableNetworkCache
option - #358 - If you are using VS Code 1.11, set the undocumented property
showAsyncStacks
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
2.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
andverboseDiagnosticLogging
are now deprecated in favor of thetrace
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.
2.5.5
- Fix "Cannot find context with specified id" error spam - #264
2.5.4
- pathMapping doesn't work on attaching to existing tab, thanks for the PR from llgcode - Microsoft/vscode#175
- Disabled column BPs for VS Code 1.10, since they aren't supported yet.
- Don't show TypeError for watch when not at a BP - Microsoft/vscode#173
2.5.3
- Fix "Cannot read property 'line' of null", breakpoints not working - #353
2.5.2
- Fix watches being broken while stepping - Microsoft/vscode-chrome-debug-core#166
- Fix error "Error processing 'stackTrace': TypeError: Cannot read property 'scriptId' of undefined" - Microsoft/vscode-chrome-debug-core#167
2.5.1
- Just removing the 'languages' entry in package.json to work around a VS Code 1.9 issue - #348
2.5.0
- Resolving sourcemaps from https, thanks to a PR from kanongil - Microsoft/vscode-chrome-debug-core#151
- Add the 'pathMapping' property to handle cases when 'webRoot' is not enough to map URLs to local paths, thanks to a PR from llgcode - Microsoft/vscode-chrome-debug-core#147
- Implemented dynamic 'skipFiles' support, which you will also see in the
node2
debug adapter. Right click on a stack frame to skip it. VS Code 1.9+ only. Microsoft/vscode-chrome-debug-core#129 - Log expandable objects in the console, instead of just static string representations of objects - Microsoft/vscode-chrome-debug-core#145
- 'step in' with a watch sometimes opens empty editor and crashes adapter - Microsoft/vscode-chrome-debug-core#148
- Show skip frame status in callstack. With VS Code 1.9, skipped frames will be grayed out. - Microsoft/vscode-chrome-debug-core#150
- Add configurationSnippets for common launch config scenarios - #336
- Use correct sourcemaps after the page reloads - #152
- And even more bugfixes that I won't enumerate
2.4.2
- Enable
sourceMaps
by default. You no longer need to set"sourceMaps": true
in your launch config, but can set it to false to disable loading sourcemaps - #134 - Fix boolean properties showing as strings - #312
- Fix unhandled exceptions not being logged to the console - #130
2.4.1
- Fix hover not working when using sourcemaps, and scripts are not on disk - #309
2.4.0
- Change
experimentalSkipFiles
name toskipFiles
, as this feature is shipping with the Node debugger in 1.8. - Fix issues with hover by correctly applying sourcemaps to scope locations - #141
2.3.2
- Fix console.log regression in 2.3.1
2.3.1
- Fix crash when refreshing the page in some cases - #297
2.3.0
- The restart button will now refresh the page instead of relaunching Chrome (works in Insiders, or VS Code 1.8) - #91
- The
experimentalLibraryCode
setting is now calledexperimentalSkipFiles
- The
experimentalSkipFiles
setting now takes a glob pattern instead of a regex - #127 - The
experimentalSkipFiles
setting can now take sourcemapped paths to exclude - #128 - An issue with breakpoints moving around on a page refresh has hopefully been fixed - #296
- Fix crash "path must be a string" when parsing sourcemaps on some eval scripts - #268
- Fix errors when pausing in chrome extension scripts by blackboxing extension content scripts - #124
2.2.2
- Handle another format of Console.MessageAdded - #276
- Fix "Pending breakpoints resolved after refreshing the page sometimes don't bind correctly" - #279
- Strip %c color specifiers - #282
2.2.1
- Add the
experimentalLibraryCode
launch option (see README). - Log unhandled exceptions for #276
- Tweak in-box webpack configs to fit default configs that I've seen.
- Fix "Breakpoints can go to wrong lines when set in merged files on startup" #277
2.2.0
- Implement the
.scripts
command in the debug console to print all the scripts loaded in Chrome, their sourcemap details, and inferred local paths, to make it easier to debug a project's debug config. See the README for more details. - Make the "Add watch" context menu item work much more robustly.
- Fix "Console logs missing in pre-Chrome 54" #265
- Fix "sourceMapPathOverrides matching doesn't work when sourceRoot does not end in /" - Microsoft/vscode-chrome-debug-core
2.1.3
- Error handling for invalid messages from Chrome, to avoid crashing - #274
- Fix potential issue with sourcemap path handling on Windows
2.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
2.1.1
- Fix setting breakpoints before startup in scripts that don't have sourcemaps - Microsoft/vscode-chrome-debug-core#121
- Fix a certain format of sourceMappingUrl - #269
2.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
2.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
1.2.2
- Fix occasional error that can cause breakpoints to not bind
1.2.1
- Disable caching downloaded sourcemaps, hoping to fix #247
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
1.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
1.0.0 - Largest update ever!
- 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
0.4.8
- Fix for not attaching correctly when using the 'launch' config with Chrome already open - #79
- Note - as part of this, it will no longer attach to a random tab when it can't find a match using the
"url"
parameter. If that parameter is set in the launch config, there must be a match.
- Note - as part of this, it will no longer attach to a random tab when it can't find a match using the
- Make the attach retry logic more resilient.
- Support wildcards in the
"url"
parameter for 'attach' configs - #200 - Fix
NaN
andInfinity
display - #190 - Fix
sourceMapPathOverrides
doc mistake - #194, thanks @lijunle!