The syntax highlighting should appear immediately.

The backing language server should be downloaded automatically in the background.

This extension detects all .hxml files in the workspace root, and then tries to choose the best one as configuration. This decision might be wrong! To explicitly use a specific .hxml file, create a .zed/settings.json file in your project root:

{
  "lsp": {
    "haxe-language-server": {
      "initialization_options": {
        "displayArguments": ["DevEnv.hxml"]
      }
    }
  }
}

{
  "lsp": {
    "haxe-language-server": {
      "initialization_options": {
        "displayServerConfig": {
          "path": "/your/custom/haxe/here"
        }
      },
      "settings": {
        "haxe": {
          "buildCompletionCache": true,
          "displayHost": "127.0.0.1",
          "displayPort": 6001
        }
      }
    }
  }
}

The Haxe language server does not natively understand Lime projects, supporting .hxml files only. However, Lime lets you easily generate them.

Assuming that

• you have a Project.xml file in your workspace root, and
• you're targetting html5,

you can run in your favorite shell:

lime build html5
lime display html5 > html5.hxml

This creates a html5.hxml file telling Haxe which libraries to include and what platform to target. See the instructions above on how to tell Zed to use this file.

Many other Haxe toolchains can create .hxml files, including:

nme prepare html5

ceramic clay hxml web > web.hxml

To use dev Zed extensions, you will need to have Rust compiler installed.

You will also need to git clone this repository.

In the Extensions panel (Ctrl+Shift+X), click Install Dev Extension in the top right corner. Choose the location of the downloaded directory.

• tree-sitter grammar by tong
• haxe-language-server by the vshaxe team, MIT-licensed