Skip to content

Commit

Permalink
docs: fix vscode-vsce PR details (#2314)
Browse files Browse the repository at this point in the history
  • Loading branch information
karlhorky authored Jan 2, 2021
1 parent 66d0474 commit 14027c4
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion packages/gatsby/content/features/plugnplay.md
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ The following tools unfortunately cannot be used with pure Plug'n'Play install (
| --- | --- |
| Flow | Follow [yarnpkg/berry#634](https://github.com/yarnpkg/berry/issues/634) |
| React Native | Follow [react-native-community/cli#27](https://github.com/react-native-community/cli/issues/27) |
| VSCode Extension Manager (vsce) | Use the [vsce-yarn-patch](https://www.npmjs.com/package/vsce-yarn-patch) fork with the `node-modules` plugin enabled. The fork is required until [microsoft/vscode-vsce#379](https://github.com/microsoft/vscode-vsce/pull/379) is merged, as `vsce` currently uses the removed `yarn list` command |
| VSCode Extension Manager (vsce) | Use the [vsce-yarn-patch](https://www.npmjs.com/package/vsce-yarn-patch) fork with the `node-modules` plugin enabled. The fork is required until [microsoft/vscode-vsce#493](https://github.com/microsoft/vscode-vsce/pull/493) is merged, as `vsce` currently uses the removed `yarn list` command |

This list is kept up-to-date based on the latest release we've published starting from the v2. In case you notice something off in your own project please try to upgrade Yarn and the problematic package first, then feel free to file an issue. And maybe a PR? 😊

Expand Down

0 comments on commit 14027c4

Please sign in to comment.