Environment preparation and LSP setup

[digitalextremist]

Following after installing: https://github.com/zedless-editor/zedless/discussions/40#discussion-8864342

---

Since downloading is removed ( 🎊 ) we ought to put up light documentation for these:

• Environment preparation
• Setting up LSP properly

I noticed a fair number of warnings due to unreferenced variables and the like, which is to be expected in this situation, but can be removed also, which is ticketed separately ( #41 ) as a placeholder.

@max-privatevoid would you please give some examples of what you said here, and how you wired this up: https://github.com/zedless-editor/zedless/issues/39#issuecomment-3265750735

[digitalextremist]

Am running now, and will contribute a build guide for Linux soon.

I do have formatting working on-save. The issue I am facing is getting an LSP / linter to report back errors/warnings into the editor.

Do you have an example of a working configuration for this @max-privatevoid?

I know you are not using TypeScript but the concept ought to be the same. I am not seeing working default settings to model after.

Any help would be appreciated; this seems like the last roadblock before daily use, then I will be able to help tune the experience.

[digitalextremist]

Seems like I am almost there.

I am running the equivalent of --foreground so that I see the log in real time.

At first ( and still, now ) I was seeing an inscrutable ( to me ) error from any/all language servers:

wasm trap: cannot enter component instance

What got me headed toward Zedless in earnest was seeing >10gb RAM usage in the prior IDE, and never-ending increases in resource drain no matter what. I could not switch over to bun for everything and was forced to use node.js as well, though I carefully purged it everywhere else. I pretty much just needed TypeScript linting and formatting, and to be able to work uninterrupted for an entire day/session, rather than be yanked out of flow every 20-90 minutes ( a form of torture ).

I fumbled around and eventually settled upon a configuration like this, for each of the languages that matter to me:

  "languages": {
    "TypeScript": {
      "linter": {
        "external": {
          "command": "/home/de/.bun/bin/bunx",
          "arguments": [
            "oxlint",
            "--format",  //de <--- This line and the next made the difference
            "json",
            "--quiet",
            "{buffer_path}"
          ]
        }
      },
      "formatter": {
        "external": {
          "command": "/home/de/.bun/bin/bunx",
          "arguments": ["prettier", "--stdin-filepath", "{buffer_path}"]
        }
        // "code_actions": {
        //   "command": "/home/de/.bun/bin/bunx",
        //   "arguments": ["oxlint", "--stdin-filepath", "{buffer_path}"]
        // }
      }
    },
  }

Now, I get this coherent error message:

2025-09-14T07:06:56-07:00 ERROR [editor] Failed to format buffer via external command: /home/de/.bun/bin/bunx
Caused by:
    command failed with exit code Some(2):
    stdout: 
    stderr: [error] REDACTED_FULL_PATH_AND_FILE_NAME.ts: SyntaxError: Declaration or statement expected. (40:1)
    [error]   38 | };
    [error]   39 |
    [error] > 40 | export REDACTED = Object.keys(REDACTED)
    [error]      | ^
    [error]   41 |
    [error]   42 | function REDACTED(): { [key: string]: string[] } {
    [error]   43 |   const summary: { [key: string]: string[] } = {};

Right there I had forgotten const after export was all. Normally I would see a red squiggly line under the offending area.