-
-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to get working with neovim #66
Comments
Thanks, I'll take a look. I think we've fixed this once before... |
@Issafalcon I see from #38 that you are also using neovim. Are you able to run 1.0.0 successfully in neovim? |
@aslakhellesoy - It's been a while since I've done anything with cucumber actually, but I have started using mason like @darrinholst instead of the previous methods for installing LSPs, so it might have changed how setup works. When I get chance, I'll try and use it again. Might need to update my Neovim version as well. |
I was able to get a better stack trace. Seems that it's expecting a URL and receiving a file path. (I know little more about wasm than what the acronym means)
|
I found the end of the 🐰 hole - tree-sitter/tree-sitter#1765 |
Ooooh that's some serious burrowing @darrinholst! Thanks for doing the digging! |
I released Please reopen this issue if the problem persists. |
Still seeing the same thing when node is 18.6.0. It has the
On a side note, I did try it with node 16.17.1 and it seems to be working although the thing I really wanted it for was formatting which isn't working (probably a separate issue from this one). This is what I'm seeing...
|
Hi @aslakhellesoy - I just tried running using the following versions of tools:
I get a series of errors when it tries to load the wasm files:
The wasm files are there in the dist folder where mason installs them Beyond that, the LspLogs throw lots of the following errors on parsing:
Naturally, the language server is now unusable. |
Thanks for the details. The language server is embedded as a library in the Cucumber vscode extension, where it works without any problems. I believe VSCode runs on Node 16. It’s not a priority for me to make it work as a standalone CLI, but I’d be delighted if someone could figure out why it’s not working, and submit a PR. |
Closing as I have a workaround for what I need for formatting (and it's probably just me in the middle of the Cucumber-Vim-Neovim Venn diagram anyway 😏 ). I'd like to get it working as well, but I think we're blocked on tree-sitter/tree-sitter#1765 for now. I'll keep an eye on that and come back to this when it's resolved. |
👓 What did you see?
Tried using the language server in neovim mostly just to get feature file formatting, but getting the following error...
[ERROR][2022-10-10 08:03:10] ...lsp/handlers.lua:485 "Cucumber Language Server 1.0.0: Unhandled Rejection at promise: [object Promise], reason: TypeError: Failed to parse URL from /Users/darrinholst/.local/share/nvim/mason/packages/cucumber-language-server/node_modules/@cucumber/language-server/node_modules/web-tree-sitter/tree-sitter.wasm"
✅ What did you expect to see?
Not an error. 😏
📦 Which tool/library version are you using?
🔬 How could we reproduce it?
Sorry, I'm not the best at debugging neovim lsp errors. It seems that others have gotten this to work so it's a shot in the dark to see if anyone else is having this issue. I'd be happy to debug it locally if anyone has any tips or tricks on how to do that. I have been able to work around the formatting that I was in search of by using
@cucumber/gherkin-utils
directly, but it would be nice to get it working with lsp.This text was originally generated from a template, then edited by hand. You can modify the template here.
The text was updated successfully, but these errors were encountered: