microsoft
/
vscode-chrome-debug
зеркало из
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность
vscode-chrome-debug/CHANGELOG.md

18 KiB
Исходник Ответственный История

3.1.2

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

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

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 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.

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

2.5.1

  • Just removing the 'languages' entry in package.json to work around a VS Code 1.9 issue - #348

2.5.0

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 to skipFiles, 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 called experimentalSkipFiles
  • 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

2.1.0

2.0.0

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!

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.
  • Make the attach retry logic more resilient.
  • Support wildcards in the "url" parameter for 'attach' configs - #200
  • Fix NaN and Infinity display - #190
  • Fix sourceMapPathOverrides doc mistake - #194, thanks @lijunle!