Skip to content

Update npm package dependencies, in order to support the latest version of the Language Server Protocol#3

Merged
Araq merged 10 commits into
nim-lang:mainfrom
nickysn:inlay_hints_support
Nov 30, 2023
Merged

Update npm package dependencies, in order to support the latest version of the Language Server Protocol#3
Araq merged 10 commits into
nim-lang:mainfrom
nickysn:inlay_hints_support

Conversation

@nickysn

@nickysn nickysn commented Nov 30, 2023

Copy link
Copy Markdown
Collaborator

Note: this pull request contains the same things as: saem/vscode-nim#134
I'm opening it here, because there was no reaction from Saem on this pull request for over a month.

I'm working on adding inlay hint support to nimsuggest and the Nim language server. Inlay hints are supported in the latest (3.17) version of the Language Server Protocol. But for this to work in VS code with this extension, the npm package vscode-languageclient needed to be updated, so this was done in this pull request. Updating the npm dependencies also resolves several known security vulnerabilities in the old versions of the packages that were used previously.

This pull request also includes fixes for compilation with Nim version 1.6.16 (the latest stable version in the 1.6.x series). There's also an addition to the compilation instructions in the README.md file - there's an extra step needed, before the package can be compiled, because the nimsuggest sources are required for compilation, however (as far as I know), they were dropped from the 'nim' nimble package.

There's also a new configuration option for tracing the communication between the VS code extension and the language server (and writing in the 'Output' window), when this extension is run in lsp mode.

@Araq Araq merged commit 78ad644 into nim-lang:main Nov 30, 2023
@nickysn nickysn deleted the inlay_hints_support branch November 30, 2023 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants