Bugs and Improvements

Severity levels: see Reporting Bugs

We really want to focus on improving the developer experience, so reports about what feels wrong in the editor matter as much as crashes.

Where to report

• A type error that's misleading, wrong or hard to read: open an issue in the luwu repository. Type checking is part of Luwu's Analysis.
• Hovers, completion, code actions, the VS Code or Zed extension, or anything else about editor support: open an issue in the luwu-lsp repository.

A short piece of code that shows the problem makes a report much easier to fix.

When diagnostics flicker or disappear

Diagnostics that flicker or vanish usually mean the language server crashed and restarted. In VS Code, open the Output panel and pick Luwu Language Server to see its log. After five crashes in three minutes VS Code stops restarting it and says so in a notification. Luwu: Reload Language Server starts it again.

To find out whether the crash is in luwu-lsp or in Luwu's Analysis:

1. Save the file you were editing when the diagnostics went away.
2. Run the same check from the command line, with the definition files your project uses:

Copyluwu-lsp analyze --defs=globals.d.luau path/to/file.luwu

• If the command crashes too, the bug is most likely in Luwu's Analysis. Report it in the luwu repository.
• If the command finishes but the editor keeps crashing, the bug is most likely in the language server. Report it in the luwu-lsp repository.

If you can't tell, report it in luwu-lsp and we'll move it.