Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

vscode-yarn

gamunu44SEE LICENSE IN LICENSE.md1.6.0

yarn commands for VSCode

multi-root ready

readme

vscode-yarn: VSCode extensions to manage yarn commands.
Releases Issues

<p align="center"VSCode-Yarn: VSCode extensions to manage yarn commands.

Getting started

You can install this awesome extension through the VSCode-Yarn.

Installation

Launch Quick Open

Paste the following command and press Enter:

ext install gamunu.vscode-yarn

Packaged VSIX Extension ↑

Download the latest .vsix release file from the GitHub repository and install it from the command line

code --install-extension vscode-yarn-*.*.*.vsix

or from within VS Code by launching Quick Open and running the Install from VSIX... command.

GitHub Repository Clone ↑

Change to your .vscode/extensions VS Code extensions directory. Depending on your platform it is located in the following folders:

  • Linux ~/.vscode/extensions
  • macOs ~/.vscode/extensions
  • Windows %USERPROFILE%\.vscode\extensions

Clone the Material Theme repository as gamunu.vscode-yarn:

git clone git@github.com:gamunu/vscode-yarn.git gamunu.vscode-yarn

Features

Commands

  • yarn init
  • yarn install
  • yarn add
  • yarn add --dev
  • yarn remove <pkg>
  • yarn start
  • yarn test
  • yarn publish [tag]

  • yarn run <script>

    Not happy with the available commands ? No problem, raw command is also available. Enter any yarn command you want.

Explorer context menu

yarn install also available in the package.json file's explorer context menu.

Context menu

Run last executed script

You can also run the last executed script by typing yarn run last....

Terminate a script

You can terminate a script with the terminate command. It uses the tree-kill module that you can find on yarn. It has different behaviors on Unix or Windows.

Order of execution of yarn commands

  1. If a package.json is opened as an active editor/focused tab yarn will be invoked on it.
  2. If the package.json is explicitly defined in the configuration yarn will invoke on it.
  3. If above scenarios fail to satisfy. The extension will fallback to package.json in project root folder.

Settings

  • yarn.runInTerminal Defines whether the command is run in a terminal window or whether the output form the command is shown in the Output window. The default is to show the output in the output window.
  • yarn.dontHideOutputOnSuccess Keep the output panel visible when yarn execution is successful. No effect with runInTerminal. The default is to keep output window open.
  • yarn.bin Custom npm bin name, the default is yarn.
  • yarn.packageJson Default package json path. relative to current project root.
Example
{
  "yarn.runInTerminal": false,
  "yarn.dontHideOutputOnSuccess": false
  "yarn.packageJson": "src/package.json"
}

Keyboard Shortcuts

The extension defines a chording keyboard shortcut for the R key. As a consequence an existing keybinding for R is not executed immediately. If this is not desired, then please bind another key for these commands, see the customization documentation.

Contribute

Report a bug or a suggestion by posting an issue on the git repository (https://github.com/gamunu/vscode-yarn).

vscode-yarn incorporates code modified from fknop vscode-npm.

changelog

1.6 - 26th February, 2018

  • Fix for Issue 9
  • Fix for Issue 8
  • Fixed the bug context menu not correctly picking up the package.json file

1.5 - 03rd February, 2018

  • Explorer context menu for installing packages.
  • Default behavior changed to keep the output window open after executing a command. yarn.dontHideOutputOnSuccess (default true)
  • Fix for Issue 7

1.4.0 - 12th November, 2017

  • New workspace settings
    • yarn.dontHideOutputOnSuccess (default false) Keep the output panel visible when yarn execution is successful (no effect with runInTerminal)

1.3.0 - 11th September, 2017

  • New workspace settings
    • yarn.packageJson (default "") specify a default package json file path. relative to current project root.

1.2.0 - 11th May, 2017

  • Two new workspace settings
    • yarn.runInTerminal (default false), this will execute commands in a terminal window.
    • yarn.bin (default env Yarn bin path), this can be used to set a custom Yarn location.

1.1.0 - 12th April, 2017

  • Changed yarn commands execution behavior, Fix for Issue 1

  • If a package.json is opened as an active editor yarn will be invoked on it.

  • If the above scenario fails to satisfy fallback to package.json in project root folder.