Skip to content

Commit beaf2fc

Browse files
committed
[ci skip] Update CONTRIBUTING.md
1 parent 440f3ed commit beaf2fc

File tree

1 file changed

+0
-6
lines changed

1 file changed

+0
-6
lines changed

.github/CONTRIBUTING.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,19 +6,13 @@ We are following [**the contributing guideline of Marp team projects**](https://
66

77
## Setup repository
88

9-
The most important difference of Marp for VS Code from common Marp team packages is **using npm package manager instead of yarn**.
10-
119
```bash
1210
git clone https://github.com/marp-team/marp-vscode.git
1311
cd ./marp-vscode
1412

1513
npm install
1614
```
1715

18-
We had met the trouble of VSIX packaging with yarn many times. [An opened issue in vscode-vsce](https://github.com/microsoft/vscode-vsce/issues/432) is not so received attentions from developers in spite of that many extension authors are using yarn.
19-
20-
Thus, using `npm` is the safest way to develop stable VS Code extension continuously for now.
21-
2216
## Development
2317

2418
Typically using VS Code's debugger is good. See launch configurations on [`.vscode/launch.json`](../.vscode/launch.json).

0 commit comments

Comments
 (0)