-
Notifications
You must be signed in to change notification settings - Fork 37
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #189 from CodinGame/vscode-1.82.0-monaco-0.43.0
Update to vscode v1.82.0 monaco-editor v0.43.0
- Loading branch information
Showing
15 changed files
with
756 additions
and
591 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
# How to upgrade to next vscode and monaco-editor versions | ||
|
||
## Preparation | ||
|
||
- It is assumed `monaco-vscode-api`, `vscode` and `monaco-editor` repos are cloned locally on the same directory level. `monaco-editor` is not required, but helpful | ||
|
||
## vscode repository | ||
|
||
- Get the new vscode commit from the new monaco-editor release version (in the package.json there is a `vscodeRef` field) | ||
- Go to the vscode repo directory, reset to the previous vscodeRef commit | ||
- Apply the current patch: `patch -p1 < ../monaco-vscode-api/scripts/vscode.patch` | ||
- `git stash` | ||
- Checkout new vscodeRef commit | ||
- `git stash pop` | ||
- Resolve conflicts / update code (e.g. broken imports) | ||
- Generate new patch: `git diff --staged > ../monaco-vscode-api/scripts/vscode.patch` | ||
|
||
## monaco-vscode-api repository | ||
|
||
- Update `monaco-editor` and other dependencies and update to the new `vscodeRef` from above | ||
- Run `npx @vscode/dts dev` afterwards to update the `vscode.proposed.xxx.d.ts` files. It fixes potential errors in `api.ts` | ||
- Wait for the new vscode version to be downloaded and built | ||
- Fix errors, adapt code, build, include the `vscode.patch` into this commit | ||
- Do not hesitate to run the eslint autofix, it gets rid of the majority of your errors | ||
- Implement missing services. This is easily observable seem when running the demo (see next point) | ||
- Update demo | ||
- Update dependencies | ||
- Implement improvements dependening on the new features available from vscode (optional) | ||
|
||
## Hints | ||
|
||
Use repo log viewers and check the last update branch when in doubt |
Oops, something went wrong.