* 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
* linux - remove `--no-sandbox` flag
We should not disable sandbox on Linux.
We only added this to support running on Kernel <= 3.8 where setuid sandbox is used.
* fix ci
* add some docs
* Update to Electron 2.0-beta.7
* back to exploration build
* fix compile errors
* workaround build issue (go back to 1.24.0)
* bump to 1.25.0
* use electron 2.0.2
* revert custom distro
* Update to Electron 2.0.0-beta.7
* bump to electron 2.0.0-beta.7
* localStorage - workaround birthtime rounding issues that clear workspace storage
* fix compile error
* workaround #47569
* localStorage - add telemetry for successful migration
* increment to localStorageTimers4
* localStorage - allow to restore from backup if starting with 1.7.x again
* logLocalStorageMigrationStatus only on insider
* back to official distro
* 💄
* still use exploration distro
* remove GTK3 emoji picker which does not seem to work
* 💄
* electron@2.0.0-beta-1
* Update distro
* Update electron.d.ts to 2.0.0-beta.1
* Disable asar as it causes a native crash
* Adopt Module._resolveLookupPaths ASAR patch
* electron 2.x - restore inspector URL in extension host
* electron 2.x - adopt context menu callback for onHide
* electron 2.x - remove workaround for https://github.com/electron/electron/issues/10442
* electron 2.x - update node.d.ts
* electron 2.x - update node.d.ts to 8.9.x
* electron 2.x - keep node.d.ts changes to a minimum
* electron 2.x - remove workaround for https://github.com/electron/electron/issues/10862
* electron 2.x - bump to 2.0.0-beta2
* bump to 2.0.0-beta.3
* Context menu: selecting "Rename" does not put focs into rename box (fix#45601)
* quality "exploration" for easier testing
* empty commit
* push a workaround for #45700
* Certain themes show UI artifacts over activity bar icons (fixes#45700)
* better fix for #45700
* bump to 2.0.0-beta.4
* another fix to prevent flickering for #45700
* avoid remote access in index.js
* bump distro commit
* electron 2.x - do not use --debug anymore
* bump electron to 2.0.0-beta.5
* electron 2.x - add libgtk-3-dev as build dependency for Linux 64
* electron 2.x - workaround freeze on linux on startup
* bump local storage telemetry key
* electron 2.x - do a one time backup of local storage
* enable ELECTRON_ENABLE_LOGGING on macOS at least
* 2.0.0-beta.6
* Fix ctrl+shift+e not focusing explorer on Linux
* distro - use GH electron builds for now
* use electron 1.3.4
* ATOM_SHELL_INTERNAL_RUN_AS_NODE => ELECTRON_RUN_AS_NODE
* OSS input
* update electron.d.ts
* workaround for #8708
* bump oniguruma and chokidar with custom fsevents
* build with appveyor config from master
* oops, still use ELECTRON_RUN_AS_NODE
* use electron 1.3.5
* optional fsevents
* add cat.exe to workaround output issues
* use cat for tests
* remove some now obsolete ELECTRON_NO_ATTACH_CONSOLE
* also pipe output to cat for code.sh on windows
* unset ELECTRON_RUN_AS_NODE for appveyor
* fix tfs builds?
* fix build
* fix build?
* use cat only when running tests locally