fe1ba6140e
Merge branch 'main' into tyler/shouldonlypush
2023-03-03 10:16:27 -08:00
cd4fe8e3d2
chore: remove webpack and tsb, use esbuild ( #1581 )
...
* chore: remove webpack and tsb, use esbuild
Fortunately we don't depend on any extension global in integration
tests, so moving over was relatively easy. Also adopt the esbuild-
powered `tsx` loader for mocha unit tests.
- 😻 Build time 50s -> 1.4s
- 🚀 Extension.js size 1,630KB -> 1280KB -- mostly better treeshaking
Fixes #1575
* fix tests for windows path sensitivity
2023-03-01 16:29:07 -08:00
581f6451f6
fix: unbound breakpoints in sourcemaps on Chrome 112 ( #1580 )
...
Chrome Dev (112) no longer has any stackframes for instrumentation
breakpoints, which was resulting in a thrown error.
Fixes #1567
2023-02-28 11:50:57 -08:00
87eaa14463
fix: Reflect.hasOwnMetadata is not a function in debugServer ( #1579 )
...
Fixes #1577
2023-02-28 11:45:50 -07:00
b208586d8e
fix: recursive source map resolution parsing ignored locations ( #1578 )
...
* fix: recursive source map resolution parsing ignored locations
Fixes https://github.com/microsoft/vscode/issues/169733
* fix long-standing test flake
2023-02-27 17:44:42 -08:00
46c6e8751c
fix: repl stacktrace with renames showing too much info ( #1576 )
...
* fix: repl stacktrace with renames showing too much info
Fixes #1259
* fixup! tests
2023-02-24 07:23:00 +00:00
3b33a41625
Merge pull request #1574 from microsoft/release/1.76
...
Release/1.76
2023-02-22 10:46:54 -08:00
f7cc6bed50
1.76.0
2023-02-22 10:43:39 -08:00
b5785dd544
docs: prep for 1.76
2023-02-22 10:43:21 -08:00
188f552ca9
fix: source map resolution in parent workspace folder paths not working ( #1573 )
...
* fix: source map resolution in parent workspace folder paths not working
Fixes https://github.com/microsoft/vscode-js-debug/issues/1554#issuecomment-1420520834
* fix for auto-updated build agents
2023-02-22 11:05:25 -07:00
8d34776af0
fix: don't fail on dynamic config provisioning if no package.json's exist ( #1569 )
...
Fixes https://github.com/microsoft/vscode/issues/172522
2023-02-22 05:55:54 +01:00
c22379db98
fix: resolveSourceMapLocations not being auto-filled for ext host debug ( #1568 )
...
See https://github.com/microsoft/vscode-js-debug/issues/1554\#issuecomment-1420520834
2023-02-22 05:55:42 +01:00
1c7f934782
Revert "Merge pull request #1481 from microsoft/complex-sourcemap-names" ( #1566 )
...
* Revert "Merge pull request #1481 from microsoft/complex-sourcemap-names"
This reverts commit 7b5e81dbb06130f21c78https://github.com/microsoft/vscode-js-debug/issues/1561
Just undo this change (made last release) in this one. I'm not sure if
it's possible to support this, at least without changes upstream in Babel.
* more
2023-02-21 08:03:34 -08:00
1994c1e785
chore: update tests and build ( #1565 )
2023-02-21 09:00:23 +01:00
582e6c5b86
chore(deps): bump cacheable-request and got ( #1559 )
...
Bumps [cacheable-request](https://github.com/jaredwray/cacheable-request ) to 10.2.7 and updates ancestor dependency [got](https://github.com/sindresorhus/got ). These dependencies need to be updated together.
Updates `cacheable-request` from 7.0.2 to 10.2.7
- [Release notes](https://github.com/jaredwray/cacheable-request/releases )
- [Commits](https://github.com/jaredwray/cacheable-request/commits )
Updates `got` from 11.8.5 to 12.5.3
- [Release notes](https://github.com/sindresorhus/got/releases )
- [Commits](https://github.com/sindresorhus/got/compare/v11.8.5...v12.5.3 )
---
updated-dependencies:
- dependency-name: cacheable-request
dependency-type: indirect
- dependency-name: got
dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-14 16:56:59 +01:00
9c9a3f3a82
chore(deps): bump http-cache-semantics from 4.1.0 to 4.1.1 ( #1546 )
...
Bumps [http-cache-semantics](https://github.com/kornelski/http-cache-semantics ) from 4.1.0 to 4.1.1.
- [Release notes](https://github.com/kornelski/http-cache-semantics/releases )
- [Commits](https://github.com/kornelski/http-cache-semantics/compare/v4.1.0...v4.1.1 )
---
updated-dependencies:
- dependency-name: http-cache-semantics
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-14 16:56:46 +01:00
fd60864981
chore(deps): bump decode-uri-component from 0.2.0 to 0.2.2 ( #1465 )
...
Bumps [decode-uri-component](https://github.com/SamVerschueren/decode-uri-component ) from 0.2.0 to 0.2.2.
- [Release notes](https://github.com/SamVerschueren/decode-uri-component/releases )
- [Commits](https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.2 )
---
updated-dependencies:
- dependency-name: decode-uri-component
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-14 16:56:18 +01:00
a12550dbc8
chore(deps): bump loader-utils from 2.0.3 to 2.0.4 ( #1450 )
...
Bumps [loader-utils](https://github.com/webpack/loader-utils ) from 2.0.3 to 2.0.4.
- [Release notes](https://github.com/webpack/loader-utils/releases )
- [Changelog](https://github.com/webpack/loader-utils/blob/v2.0.4/CHANGELOG.md )
- [Commits](https://github.com/webpack/loader-utils/compare/v2.0.3...v2.0.4 )
---
updated-dependencies:
- dependency-name: loader-utils
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-02-14 16:56:06 +01:00
4d2a78523b
fix: support rich ANSI output for complex logs ( #1547 )
...
Fixes https://github.com/microsoft/vscode/issues/172868
This now works as of https://github.com/microsoft/vscode/pull/172880
2023-02-03 11:58:51 -08:00
dc55084d06
move to main since the changes are in
2023-02-02 16:18:23 -05:00
cd3750530c
use a package.nls.json
2023-02-02 15:35:16 -05:00
ce3fc45628
try packagenlspath
2023-02-02 14:33:30 -05:00
54944368ad
Push localization strings
2023-02-02 09:44:54 -05:00
7bb672707d
chore: remove implicit activation events ( #1541 )
...
* chore: remove implicit activation events
For https://github.com/microsoft/vscode-internalbacklog/issues/3442
* fix build
2023-02-01 15:42:45 -08:00
d9b8ae334a
fix: only show pretty print actions when debugger is stopped ( #1540 )
...
Fixes #1539
2023-02-01 09:52:48 -08:00
df22101629
fix: misleading error for DAP-based consumers on missing cwd ( #1538 )
...
Fixes #1517
2023-01-30 15:09:05 -08:00
4a1129e11a
fix: expansion of non-primitive getters not working ( #1536 )
...
Fixes #1525
2023-01-30 12:34:08 -08:00
a9cc9c0073
fix: adopt new test-electron to fix windows test timeouts ( #1535 )
2023-01-30 20:46:29 +01:00
7716940929
fix: put extracted locals in the right place for l10n ( #1534 )
2023-01-30 11:00:07 -08:00
08183eed58
fix: typeerror for users of vsDebugServer.bundle.js ( #1533 )
...
Fixes #1502
2023-01-30 10:03:18 -08:00
cf0888942d
fix: skipFiles being slow in remotes ( #1532 )
...
Fixes https://github.com/microsoft/vscode/issues/170412
We were not rebasing remote paths correctly in the initial launch,
which caused the fallback logic to kick in and manually apply skipFiles
to every single script (and recompile globs), which was quite slow.
And add a test that I wrote while barking up the wrong tree.
2023-01-23 16:39:48 -08:00
8a0cb43445
Merge pull request #1531 from microsoft/release/1.75
...
release 1.75
2023-01-23 13:30:16 -08:00
27cf00198b
1.75.0
2023-01-23 13:01:04 -08:00
2f90537615
docs: for 1.75
2023-01-23 13:00:49 -08:00
6d4d41dfb5
fix: shutdown of debug adapter being slow ( #1530 )
...
This iteration we moved to named pipes for the connection to VS Code.
This exposed a race that wasn't hit for TCP connections: the destroy
call for streams was being invoked on the next tick after calling
transports' send(), which could be before the write happened.
The result was the DAP terminated() event didn't get sent through so
VS Code was just timing out the session after a second, which looked janky.
2023-01-23 12:00:27 -08:00
ba4c7a5891
fix: warnings of symlinks on windows ( #1529 )
...
The turbo glob stream was not emitting path.sep, so its paths didn't match source files and caused extraneous warnings about symlinks
2023-01-23 11:40:26 -08:00
e3488137f3
chore: bump vscode-nls for build fix ( #1528 )
2023-01-23 11:22:08 -08:00
ff4f4f845f
fix: build error ( #1521 )
...
Started refactoring stuff with the l10n migration, but aborted them and forgot to undo all the changes
2023-01-18 08:08:59 -08:00
175d9120d2
chore: adopt new localization pipeline ( #1515 )
...
* chore: adopt new localization pipeline
Fixes https://github.com/microsoft/vscode/issues/164438
* update
* add l10n path
* update
* update
* fix function name
* fixup
2023-01-14 13:30:20 -08:00
749f75d6b2
fix: error in vsDebugServer ( #1514 )
2023-01-12 09:46:40 -08:00
bd7ea14f3b
fix: typo in network fallback ( #1513 )
...
Whoops. Some code I couldn't test locally.
2023-01-12 09:20:57 -08:00
afac00cf6a
fix: followup for vscode#168013 ( #1512 )
...
* fix: followup for vscode#168013
* fixup! pr comments
2023-01-09 11:38:47 -08:00
0f522b9872
fix: don't hardcode generated source types as javascript ( #1508 )
...
Fixes https://github.com/microsoft/vscode/issues/168013
We don't know if a source type is actually JavaScript. Just let the editor guess instead of reimplementing mimetype detection ourselves
2023-01-05 16:52:03 -06:00
1d60d6e07a
fix: publishing not working ( #1504 )
...
The marketplace apparently started blocking extension publishing if the
readme includes any svg references. So just delete the star/version badges.
2023-01-03 12:30:50 -05:00
352d49ce82
fix: provide memory reference for evaluate expressions ( #1500 )
...
Found when looking at https://github.com/microsoft/vscode/issues/164124 ]
2022-12-30 17:08:16 -08:00
bc604e0305
Adding support to EvaluationOptions from dap. ( #1323 )
...
* Adding support to EvaluationOptions from dap, as discussed in this issue: https://github.com/microsoft/vscode-js-debug/issues/1315
* Fix tests
* Pushing generated file after merge.
2022-12-30 08:45:45 -08:00
86a9efa19c
chore(deps): bump json5 from 2.2.0 to 2.2.2 ( #1499 )
...
Bumps [json5](https://github.com/json5/json5 ) from 2.2.0 to 2.2.2.
- [Release notes](https://github.com/json5/json5/releases )
- [Changelog](https://github.com/json5/json5/blob/main/CHANGELOG.md )
- [Commits](https://github.com/json5/json5/compare/v2.2.0...v2.2.2 )
---
updated-dependencies:
- dependency-name: json5
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2022-12-30 08:31:10 -08:00
ac3199870a
refactor: add turbo mode for the breakpoint predictor ( #1498 )
...
Fixes #1149
Fixes https://github.com/microsoft/vscode/issues/167911
This does some overall system optimization for how the breakpoint
predictor works. It achieves performance comparable to the VS Code API
ripgrep globbing, with plain JS. And by using plain JS, we can do more
optimizations in a future PR.
Previously, we had an `ISearchStrategy` type that globbed for all
sourcemap URIs in a target folder, and emitted those. Then the breakpoint
predictor had an mtime-based cache to decide whether it would parse the
sourcemap or not.
This moves the caching responsibility into `ISearchStrategy`, which then
takes a two-phase approach to processing files, allowing it to cache the
intermediate result the breakpoint predictor previously cached itself.
This means that:
- Files never need to be read if their mtime doesn't change
- When starting a new child session, we optimize further and don't stat
compiled files that didn't previously reference the sourcefile. (We
still stat all directories to see if there are new files to pick up)
Some performance numbers:
- vscode#167911 time on my computer going from 33s -> 16s
- typescript: time to run mocha tests 52s -> 22s (without outFiles configured)
The new search strategy can be disabled by setting
`enableTurboSourcemaps: false` in your launch.json.
2022-12-30 10:09:47 +01:00
128140f1e5
fix: support launching chrome dev/beta as default fallbacks ( #1496 )
...
Fixes #1489
2022-12-28 11:15:50 -08:00
e8808b3efa
fix: reduce number of ports used by debugger ( #1495 )
...
A debt item I've been meaning to address for a while anyway. Though we
still want to support port servers for VS debug.
Should fix https://github.com/microsoft/vscode/issues/169182
2022-12-27 15:03:42 -08:00
Connor Peet
dependabot[bot]
Tyler James Leonhardt
Thays Grazia
