Skip to content

Conversation

lukel97
Copy link
Collaborator

@lukel97 lukel97 commented Apr 22, 2019

No description provided.

@lukel97
Copy link
Collaborator Author

lukel97 commented Apr 22, 2019

Forgot to mention that some of the dependencies were updated through npm audit fix

package.json Outdated
"lru-cache": "^4.1.3",
"request": "^2.86.0",
"request-promise-native": "^1.0.5",
"vscode-languageclient": "^4.4.0"
"vscode-languageclient": "5.3.0-next.4"
Copy link
Collaborator

Choose a reason for hiding this comment

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

This looks like an "under development" version?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, I'm not sure when it is planned on being released. This PR is not blocking anything though so we can wait until there is a stable release

Copy link
Collaborator

Choose a reason for hiding this comment

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

I would hate to break things for users out there.

@alanz
Copy link
Collaborator

alanz commented Jun 7, 2019

@bubba I am pretty sure this should be fixable now, given vscode 1.35.0 is now out.

@alanz
Copy link
Collaborator

alanz commented Jun 7, 2019

And according to https://www.npmjs.com/package/vscode-languageclient, current version is 5.2.1

@lukel97
Copy link
Collaborator Author

lukel97 commented Jun 8, 2019

@alanz conflicts resolved!

@@ -245,7 +245,7 @@
"lru-cache": "^4.1.3",
"request": "^2.86.0",
"request-promise-native": "^1.0.5",
"vscode-languageclient": "^4.4.0",
"vscode-languageclient": "5.3.0-next.5",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Doesn't the next suffix mean you have to be on the dev channel for vscode?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

No, the vscode version is constrained from the engines.vscode field from what I can tell: I tried bumping it to 1.35 today and I got an error when installing it with my older version of vscode. vscode-languageclient is just the library for connecting vscode extension APIs to LSP

@alanz
Copy link
Collaborator

alanz commented Jun 8, 2019

@bubba I think the vscode-languageclient needs to be 5.2.1

@lukel97
Copy link
Collaborator Author

lukel97 commented Jun 8, 2019

The progress APIs/plugs are only in 5.3.x microsoft/vscode-languageserver-node@dbe6494

@lukel97
Copy link
Collaborator Author

lukel97 commented Jun 13, 2019

@alanz is this good to go?

@alanz
Copy link
Collaborator

alanz commented Jun 14, 2019

@bubba yes, will do a release today some time

@alanz alanz merged commit 2f304a6 into haskell:master Jun 16, 2019
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