LuaLS / LuaLS/lua-language-server
Language Server Quits (installed from `winget`)
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 4.4k
- Forks
- 442
- PR merge metrics
- No merged PRs in 30d
Description
### How are you using the lua-language-server?
Command Line
### Which OS are you using?
Windows
### What is the issue affecting?
Other
### Expected Behaviour
The language server should run when installed via `winget`.
### Actual Behaviour
Running the language server gives me:
`PS C:\Users\{USERNAME}> lua-language-server.exe
C:\Users\{USERNAME}\AppData\Local\Microsoft\WinGet\Links\lua-language-server.exe: cannot open (bootstrap.lua): No such file or directory`
### Reproduction steps
1. Install via `winget`: `winget install luaLS.lua-language-server`
2. Run `lua-language-server` from the command line
### Additional Notes
Granted, this might be unrelated to this GitHub repository and should be mentioned on the winget-pkgs repository instead, but I also am not sure of how this should be fixed or, perhaps, the winget package is maintained from the authors here. Either way, there was a similar discussion mentioning this error, but that was also not on Windows and I'm unsure if any fixes from there can be applied for this scenario.
### Log File
N/A
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking the `winget` package `LuaLS.lua-language-server` and the reported `lua-language-server.exe` command on Windows, since no repository file or test is named. Determine whether the failure belongs in this repository or `winget-pkgs`; done means the installed command can locate `bootstrap.lua` and start successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100