search

nvarner / typst-lsp

A brand-new language server for Typst, plus a VS Code extension
MIT License
1.2k stars 78 forks source link

VS Code extension cannot find a valid typst-lsp binary #301

Open betoma opened 1 year ago

betoma commented 1 year ago

Issue

When I create a new .typ file or activate the extension, I receive the following error message from the Typst LSP extension: Failed to activate typst-lsp: Error: Could not find a valid typst-lsp binary. Bundled: Failed to launch '/home/bethany/.vscode/extensions/nvarner.typst-lsp-0.9.5-linux-x64/out/typst-lsp': return status: 1 In PATH: Failed to launch 'typst-lsp': error: spawnSync typst-lsp ENOENT

I have not used my Typst LSP extension since a much older version, so it's possible that this problem predates this version of Typst. I found two similar issues to this one, but both are marked "closed" and were purportedly fixed already in this version.

Logs

"Typst Language Server" does not appear in as an option for the "Output" panel.

nvarner commented 1 year ago

This issue was fixed in code, but a release with the fix hadn't been published yet. I just triggered the release process, so in about half an hour, you should be able to test typst-lsp v0.10.0, which should fix the bug.

I'll leave the issue open for now, but I think it will be resolved in v0.10.0.

ngoetti commented 9 months ago

I encountered the following error:

Failed to activate typst-lsp: Error: Could not find a valid typst-lsp binary. Bundled: Failed to launch 'c:\Users\nickg\.vscode\extensions\nvarner.typst-lsp-0.12.0-win32-x64\out\typst-lsp.exe': return status: 3221225781 In PATH: Failed to launch 'typst-lsp.exe': error: spawnSync typst-lsp.exe ENOENT

I suspect it may be the same issue, @nvarner I did this on a new install of windows. Version 0.5 worked successfully for me.

Also, I downloaded the newest TypeScript version (not LSP) and tried running the update and compile command, but it didn't do anything and didn't even provide any console output, which is really strange.

ngoetti commented 9 months ago

I installed Typist using winget, and now the Typist-lsp plugin works as well. While doing this, I noticed that Typist has a dependency on Microsoft.VCRedist.2015+.x64, which was previously not installed. So maybe that's the reason.