Skip to content

Update vscode engine#98

Merged
wooorm merged 1 commit intoremarkjs:mainfrom
remcohaszing:update-vscode-engine
Jul 14, 2022
Merged

Update vscode engine#98
wooorm merged 1 commit intoremarkjs:mainfrom
remcohaszing:update-vscode-engine

Conversation

@remcohaszing
Copy link
Copy Markdown
Member

Initial checklist

  • I read the support docs
  • I read the contributing guide
  • I agree to follow the code of conduct
  • I searched issues and couldn’t find anything (or linked relevant results below)
  • If applicable, I’ve added docs and tests

Description of changes

It now matches https://github.com/microsoft/vscode-languageserver-node/blob/main/client/src/node/main.ts#L26, which is also the latest version of VS Code at the moment of writing.

Because this version of VS Code ships with Node.js 16, the build scripts have been updated to this version as well.

It now matches
https://github.com/microsoft/vscode-languageserver-node/blob/main/client/src/node/main.ts#L26,
which is also the latest version of VS Code at the moment of writing.

Because this version of VS Code ships with Node.js 16, the build scripts
have been updated to this version as well.
Copy link
Copy Markdown
Member

@ChristianMurphy ChristianMurphy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM,
a broader question, how to we want to handle VSCode version support in relationship to this module's own version?
Would this be considered semver major for vscode-remark?

@remcohaszing
Copy link
Copy Markdown
Member Author

Semver has a clear meaning for libraries. For user facing software such as a VSCode plugin, it’s not as meaningful. IMO the upcoming release will be major, because the extension has pretty much been rewritten from scratch, but I’m not sure how to deal with future versions.

@wooorm wooorm merged commit fd483e8 into remarkjs:main Jul 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants