This commit is contained in:
Rob Lourens 2017-04-30 12:18:21 -07:00
Родитель b5f01e9532
Коммит 34401260d1
3 изменённых файлов: 21 добавлений и 5 удалений

Просмотреть файл

@ -1,6 +1,17 @@
## 3.1.0
* Implement column breakpoints (with shift+F9) for recent Chrome versions - [Microsoft/vscode-chrome-debug-core#144](https://github.com/Microsoft/vscode-chrome-debug-core/issues/144)
* Show a quickpick with available tabs when there are multiple - [#280](https://github.com/Microsoft/vscode-chrome-debug/issues/280)
* Add `webpack:///./~/` sourcemap mapping by default - [#401](https://github.com/Microsoft/vscode-chrome-debug/issues/401)
* Add `webpack:///src/*` sourcemap mapping for create-react-app by default - [#315](https://github.com/Microsoft/vscode-chrome-debug/issues/315)
* Show exception widget for breaking on promise rejection - [Microsoft/vscode#21929](https://github.com/Microsoft/vscode/issues/21929)
* Completely fix showing empty property names as "" - [Microsoft/vscode#24143](https://github.com/Microsoft/vscode/issues/24143)
* Fix "Open or close parenthesis in file path prevents debugger from discovering the target" - [#373](https://github.com/Microsoft/vscode-chrome-debug/issues/373)
* Remove "unimplemented console API" warning
* Specify languages for creating a launch config when none is set up - [#334](https://github.com/Microsoft/vscode-chrome-debug/issues/334)
## 3.0.1
* Fix "Windows - Electron app fails to start after upgrading to 3.0.0" [#407](https://github.com/Microsoft/vscode-chrome-debug/issues/407)
* On Windows, the code to prevent Chrome from closing when opening Chrome Devtools [#116](https://github.com/microsoft/vscode-chrome-debug/issues/116) is now not enabled when specifying a runtimeExecutable, until I find a better solution.
* Fix "Windows - Electron app fails to start after upgrading to 3.0.0" - [#407](https://github.com/Microsoft/vscode-chrome-debug/issues/407)
* On Windows, the code to prevent Chrome from closing when opening Chrome Devtools - [#116](https://github.com/microsoft/vscode-chrome-debug/issues/116) is now not enabled when specifying a runtimeExecutable, until I find a better solution.
## 3.0.0
* Enable userDataDir by default - [#210](https://github.com/microsoft/vscode-chrome-debug/issues/210)

Просмотреть файл

@ -1,7 +1,7 @@
{
"name": "debugger-for-chrome",
"displayName": "Debugger for Chrome",
"version": "3.0.1",
"version": "3.1.0",
"icon": "images/icon.png",
"description": "Debug your JavaScript code in the Chrome browser, or any other target that supports the Chrome Debugger protocol.",
"author": {
@ -21,7 +21,7 @@
],
"license": "SEE LICENSE IN LICENSE.txt",
"dependencies": {
"vscode-chrome-debug-core": "3.15.0",
"vscode-chrome-debug-core": "3.15.3",
"vscode-debugadapter": "1.19.0-pre.0"
},
"devDependencies": {

Просмотреть файл

@ -2,6 +2,11 @@ const globalCode = 'page loaded';
console.log(globalCode);
function locals() {
function consoleDotLog(m) {
console.log(m)
}
Promise.resolve().then(() => consoleDotLog('handler 1')).then(() => consoleDotLog('handler 2'));
setTimeout(() => {
let x = 1;
}, 1000);
@ -45,7 +50,7 @@ newlines`;
var str = 'hello';
var xyz = 1;
var obj = { a: 2, get thing() { throw 'xyz'; }, set thing(x) { } };
xyz++; xyz++; xyz++;
xyz++; xyz++; xyz++;
anotherFn(fn);
fn();