* 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
* Test using nvmrc in CI
* Force run yarn
* fix
* Bump nvmrc to latest
* Revert "Force run yarn"
This reverts commit af741f37d5.
* Make all jobs use node from nvmrc
And install node-gyp where needed
* Simplify distro
Also a ton of drive-by fixing around builds:
- simplified many oneliners
- fixed missing custom npm registry call setups
- remove unnecessary and duplicate work during builds
- many many fixes
actually run
ok run it for real
actually work
parameter syntax
monaco
logging
env var is always string
use variables
use global params
try idea to stop looping
move variables
wrap in quotes
rename all the artifacts
try downloading
up timeout
misc
underscore
add auth
log everything we need to
typo
typo
publish linux client archives too
renamed all that needed to be renamed
better error handling
raname windows assets
first attempt at letting new code handle releasing with macOS
move to $env
remove gate
include updated createAsset.js
onboard windows client
include js
add linux client
add built js
move over all publishing
update distro
use branch name?
processed artifacts and fix win32 server platforms
publish what artifacts were published
use download and more more to powershell
put it all in exec
actually in directory
fix path again
create file to be uploaded
move to all PowerShell
rename to publish and clean up code
update createAsset
use distro 2
more commented out code and add displayNames
address feedback
Use `snap pack --compression=lzo` instead of letting snapcraft pack the final
snap, as the current snapcraft.yaml is not setup to use any base in it, and as
such is missing the new feature for configuring the compression of the final
snap.
Signed-off-by: Ian Johnson <ian.johnson@canonical.com>
* chore: bump electron@9.0.5
* remove exploration config
* fix compile error
* fix compile error
* crashReporter has to be called only once before app ready
* chore: bump electron@9.1.0
* enable LayoutNG
* fix cron schedule
* allow disabling appcenter crash reporting
* set additional crash reporting parameters
* start crashreporter for child process on linux
* setup crash parameters only once
* remove unused crashReporter.guid
* address review feedback
* reuse argv.json for storing crash reporter id
* remove trailing commas
* update localized name
* update argv based on telemetry optout
* update initial config based on setting
* fix conditional errors
* remove telemetry.enableCrashReporter
* move default crash reporter config to electron-main
* update comment for ext host crash reporting
* set default value for configuration
* some 💄 changes
* address review feedback
* do not use ES7 features in JS yet
* add app.focus({ steal: true }) usage
Co-authored-by: Benjamin Pasero <benjpas@microsoft.com>
