When executing `npm run gulp vscode-win32-x64` on the Windows platform, the `bundle-vscode` task is triggered. However, this task does not handle the path issues well, resulting in the contents of the `bootstrap-window.js` file not being injected into `workbench.js` and `processExplorer.js`.
The reason why VSCode does not encounter this issue is that the code compilation (compile-build) is performed on a Linux machine, while the Windows machine only executes the application build (vscode-win32-x64-ci will not trigger `bundle-vscode`).
Signed-off-by: Kevin Cui <bh@bugs.cc>
* badge wip
* badge wip
* testing: try out new 'badges' UI for test failures
I'm exploring some UI to make tests look better in already-busy
scenarios, like Copilot edits. We've long had these big inline message
decorations which get very noisy quickly, especially with word wrap on.
I'm exploring these smaller 'badge' type indicators. These are shown in
at most one place per test and their content length is very limited.
Clicking on them opens the traditional test error peek. Because I feel
like they are easier to see and more inviting to click, I turned off the
default behavior of opening the error peek. Making any edits in the test
case will dismiss the badge.
Closes#233028
* * make inline chat filter empty in-progress items
* show ellipses progress on request
* make inline zone animate its frame during request
* allow to resize inline chat zone
fixes https://github.com/microsoft/vscode/issues/230784
* Don't auto-scroll while chat response loads
Fixmicrosoft/vscode-copilot-release#138
* Show button all the time
* Fixes, don't auto-scroll for edit session view
* Keep autoscroll in inline and quick chat
* refactor: cleanup debt for hashing
- Adds a type to avoid direct usage of sync `hash()` for consumers
working with binary input.
- Moved the previous browser-only `sha1Hex` to `hash.ts` now that
webcrypto is quite universal, including in Node.js since 19.
- Cleaned up some code that is replaced with modern built-in functions
like `TypedArray.fill` and `padStart`.
- The `NotebookSimpleWorker` was manually calculating the hash for
its binary data (probably to avoid the same issue as #229619), so
I swapped that to use webcrypto as well which is much speedier for
large inputs (125ms vs 8ms for 10MB of data) @rebornix
Closes https://github.com/microsoft/vscode/issues/229845
* update layer checker
* feat: move from yarn to npm
* chore: skip yarn.lock files
* fix: playwright download
* chore: fix compile and hygiene
* chore: bump vsce@2.17.0
Refs 8b49e9dfdf
* test: update results for bat and sh colorizer tests
* fix: add missing lock files for windows
* fix: switch to legacy-peer-deps
* chore: update markdown-it@14.1.0
Refs 737c95a129
esbuild step in extensions-ci-pr was previously using markdown-it
from root which had userland punycode and was able to compile successfully.
* ci: increase pr timeout for windows integration tests
* chore: fix product build
* build: ignore extension dev dependency for rcedit
* build: fix working directory inside container
* build: fix dependency generation
* npm: update dependencies
* ci: use global npmrc
* ci: update cache
* ci: setup global npmrc for private npm auth
* build: fix extension bundling
* chore: sync npm dependencies
* ci: debug env variables for container
* ci: fix win32 cli pipeline
* build: fix npmrc config usage for build/ and remote/ dirs
* fix: windows build
* fix: container builds
* fix: markdown-language-features tests and bundling
```
[03:58:22] Error: Command failed: /Users/demohan/.nvm/versions/node/v20.15.1/bin/node /Users/demohan/github/vscode/extensions/markdown-language-features/esbuild-notebook.js --outputRoot /Users/demohan/github/vscode/.build/extensions/markdown-language-features
✘ [ERROR] Could not resolve "punycode"
extensions/markdown-language-features/node_modules/markdown-it/lib/index.js:14:27:
14 │ var punycode = require('punycode');
╵ ~~~~~~~~~~
The package "punycode" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.
```
Adds userland package based on beed9aee2c
* fix: container builds for distro
* chore: update yarn occurrences
* fixup! chore: bump vsce@2.17.0
Uses the closest version to `main` branch that does not
include d3cc84cdec
while still having the fix 8b49e9dfdf
* chore: sync npm dependencies
* chore: sync npm dependencies
* chore: sync npm dependencies
* chore: throw error when yarn is used for installation
* chore: add review feedback
* chore: switch exec => run where needed
* chore: npm sync dependencies
* fix: markdown-language-features bundling
```
✘ [ERROR] Could not resolve "punycode"
extensions/markdown-language-features/node_modules/markdown-it/lib/index.js:14:27:
14 │ var punycode = require('punycode');
╵ ~~~~~~~~~~
The package "punycode" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.
```
Adds missing userland package based on markdown-it/markdown-it@beed9ae,
can be removed once we update markdown-it >= 14.1.0
* ci: rename no-yarn-lock-changes.yml
* chore: sync npm dependencies
* ci: restore no-yarn-lock-changes.yml
We can disable it in a separate PR to keep the required
checks happy and also need workflow edit perms.
* chore: sync npm dependencies
* ci: rebuild cache
* ci: fix no-package-lock-changes.yml
* chore: bump distro
* chore: rm yarn.lock files
* chore: rm yarn.lock files without dependencies
* chore: add vscode-selfhost-import-aid to postinstall dirs
* chore: bump distro
