01df559c18
* chore: bump electron@15.3.0 * chore: bump node@16.x * chore: enable render process reuse * Revert "watcher - use `type` property for crash reporter location" This reverts commitbfa488dd8f. * Revert "watcher - enable crash reports on linux (#136264)" This reverts commitaf261488f8. * chore: enable crashpad on linux * chore: bump electron@15.3.1 * chore: update api changes * chore: bump @vscode/sqlite3@5.0.3 * spec: skip non-context aware module unittests * chore: fix perf hook integration with node environment * fix: adopt fs api changes * chore: fix integration tests * chore: bump electron@15.3.2 * chore: bump electron@16.0.0 * temp(macOS): kill test instances in OSS * Revert "temp(macOS): kill test instances in OSS" This reverts commit b0d796c8d64227a5ec012c060bbbee7d9da27568. * chore: update chromium version for clang downloader * some 💄 changes * align with changes * adopt more fs.rm * 💄 * chore: bump @vscode/sqlite3@5.0.4 * fix layers check to account for duplicated types from node.js * update todo for type casts * smoke - fix compile issue * chore: update module cache * watcher - fix unhandled rejection (fix #137416) * ci: update node version * enable stack dumping * update electron types to 16.x * chore: bump @vscode/sqlite3@5.0.5 Refs https://github.com/microsoft/vscode/issues/137496 * fix layer issue * add `AbortSignal` to core types * chore: update linux compile flags Refs797723ec83* ci: fix linux build * ci: update github ci cache * ci: fix remote build in github ci * ci: better fix for remote build * chore: bump azure cache * chore: fix merge conflict * :chore: update to electron@16.0.2 * chore: bump @vscode/sqlite3@5.0.7 * ci: update to gcc-4.9 for remote Refs https://github.com/microsoft/vscode/issues/137659 * ci: switch to buster for linux arm Refs https://github.com/microsoft/vscode/issues/137927 * ci: fix build on linux arm64 * ci: fix arm client compiler toolchain Refs #137927 * chore: bump electron@16.0.3 * ci: fix compile flags for the c toolchain * chore: bump electron@16.0.4 * Add experimental dark mode flag (#139109) * Add experimental dark mode flag * Apply PR feedback * chore: bump electron@16.0.6 * chore: bump electron@16.0.7 Fixes https://github.com/microsoft/vscode/issues/138792 Fixes https://github.com/microsoft/vscode/issues/139300 * chore: experimental highlight API * smoke - fix compile issue * FIXME: custom ELECTRON_RUN_AS_NODE with node worker * Revert "chore: bump electron@16.0.7" This reverts commit5fd01cf37c. * Revert "Revert "chore: bump electron@16.0.7"" This reverts commita7f1b73951. * chore: fix github linux workflow * chore: address review feedback * chore: bump electron@16.0.8 * ci: revert to stretch distro for linux arm Refs https://github.com/microsoft/vscode/issues/137927 * ci: force build * chore: update yarn.lock * address feedback * Revert "FIXME: custom ELECTRON_RUN_AS_NODE with node worker" This reverts commit7b48fa3732. * ci: fix remote folder build * chore: fix github linux ci * 🆙 `versionSpec` Co-authored-by: Benjamin Pasero <benjamin.pasero@microsoft.com> Co-authored-by: Raymond Zhao <raymondzhao@microsoft.com>
Node npm
Notice: This extension is bundled with Visual Studio Code. It can be disabled but not uninstalled.
Features
Task Running
This extension supports running npm scripts defined in the package.json as tasks. Scripts with the name 'build', 'compile', or 'watch'
are treated as build tasks.
To run scripts as tasks, use the Tasks menu.
For more information about auto detection of Tasks, see the documentation.
Script Explorer
The Npm Script Explorer shows the npm scripts found in your workspace. The explorer view is enabled by the setting npm.enableScriptExplorer. A script can be opened, run, or debug from the explorer.
Run Scripts from the Editor
The extension supports to run the selected script as a task when editing the package.jsonfile. You can either run a script from
the hover shown on a script or using the command Run Selected Npm Script.
Run Scripts from a Folder in the Explorer
The extension supports running a script as a task from a folder in the Explorer. The command Run NPM Script in Folder... shown in the Explorer context menu finds all scripts in package.json files that are contained in this folder. You can then select the script to be executed as a task from the resulting list. You enable this support with the npm.runScriptFromFolder which is false by default.
Others
The extension fetches data from https://registry.npmjs.org and https://registry.bower.io to provide auto-completion and information on hover features on npm dependencies.
Settings
npm.autoDetect- Enable detecting scripts as tasks, the default ison.npm.runSilent- Run npm script with the--silentoption, the default isfalse.npm.packageManager- The package manager used to run the scripts:auto,npm,yarnorpnpm, the default isauto, which detects your package manager based on your files.npm.exclude- Glob patterns for folders that should be excluded from automatic script detection. The pattern is matched against the absolute path of the package.json. For example, to exclude all test folders use '**/test/**'.npm.enableScriptExplorer- Enable an explorer view for npm scripts.npm.scriptExplorerAction- The default click action:openorrun, the default isopen.npm.enableRunFromFolder- Enable running npm scripts from the context menu of folders in Explorer, the default isfalse.npm.scriptCodeLens.enable- Enable/disable the code lenses to run a script, the default isfalse.