Skip to content

Releases: gamunu/vscode-yarn

v2.3.1

10 Apr 20:59

Choose a tag to compare

Bug Fixes

  • Update publish step to use MARKETPLACE_TOKEN for authentication (23bf68e)

v2.3.0

10 Apr 20:41

Choose a tag to compare

Features

  • Add GitHub Actions workflow for publishing to VSCode Marketplace (84344be)
  • Implement Yarn sidebar with npm package search and registry management (#57) (219b525)

v2.1.0

21 Feb 17:57
736b51f

Choose a tag to compare

  • Add submenus for multiple Yarn commands

Install Packages, Test, Build, Start, Run Script, Add & Save Package, Add & Save Dev Package, Remove Package, Publish, Outdated

v2.0.0

11 Sep 09:08
428dc6d

Choose a tag to compare

  • Add WSL and Multi-Workspace support

v1.7.1

14 Aug 09:16
e19f435

Choose a tag to compare

Deactivate keybinding if terminalFocus active

- Add when !terminalFocus to all Ctrl+R commands
- Fixes #19
- Fix typescript lint errors

v1.7.0

07 Dec 17:33

Choose a tag to compare

  • Fix for Issue 11
  • Add TouchBar assets and update package.json.
    TouchBar support includes:
    • yarn run test
    • yarn install
    • yarn run build
    • yarn run start
  • New workspace setting config.yarn.enableTouchbar to
    enable TouchBar support.
  • run.runInTerminal is now default to true.

v1.6.0

26 Feb 14:43

Choose a tag to compare

  • Fix the bug context menu not correctly picking up the package.json file
  • Update readme file
  • Add tslint.json
  • Add .editorconfig.json
  • Fix lint errors

v1.5.0

03 Feb 07:01

Choose a tag to compare

  • 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

v1.4.0

24 Jan 14:56

Choose a tag to compare

New workspace settings

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

v1.3.0

20 Sep 19:23

Choose a tag to compare

Add setting to explicitly specify package json path Issue 1
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 fall back to package.json in project root folder.
Fix typescript issues in init file