development/vscode
development/vscode
1
0
Fork 0
mirror of https://github.com/Microsoft/vscode synced 2024-09-29 07:51:27 +00:00
Code Issues Packages Projects Releases Wiki Activity
vscode/extensions/npm
History
Robo b5a6aa14a8
feat: switch to npm as default package manager (#226927) 
* 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
2024-09-06 22:18:02 +09:00
..
.vscode
images
src Use shell: true only on Windows (#224597) 2024-08-05 01:46:45 -07:00
.vscodeignore feat: switch to npm as default package manager (#226927) 2024-09-06 22:18:02 +09:00
extension-browser.webpack.config.js
extension.webpack.config.js
package-lock.json feat: switch to npm as default package manager (#226927) 2024-09-06 22:18:02 +09:00
package.json chore: update to electron 29 (#209818) 2024-05-11 01:20:28 +09:00
package.nls.json Add Bun as package manager to npm extension 2023-11-11 16:37:29 +00:00
README.md Add Bun as package manager to npm extension 2023-11-11 16:37:29 +00:00
tsconfig.json npm: adopt terminal quick fix api (#167664) 2022-12-02 08:20:53 -08:00

README.md

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 is on.
  • npm.runSilent - Run npm script with the --silent option, the default is false.
  • npm.packageManager - The package manager used to run the scripts: auto, npm, yarn, pnpm or bun. The default is auto, which detects your package manager based on files in your workspace.
  • 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: open or run, the default is open.
  • npm.enableRunFromFolder - Enable running npm scripts from the context menu of folders in Explorer, the default is false.
  • npm.scriptCodeLens.enable - Enable/disable the code lenses to run a script, the default is false.