Graphaxe adds a thin, workspace-aware layer on top of the existing Haxe and Lime tooling in VS Code.

What it does

build the current Graphaxe target
run or debug the current Lime target through Lime's own launcher
sync generated sources
explain the resolved project
export or open generated XML
ship Haxe snippets for common Graphaxe workflows

Commands

Graphaxe: Resolve Current Lime Target
Graphaxe: Run Current Lime Target
Graphaxe: Debug Current Lime Target
Graphaxe: Build Current Lime Target
Graphaxe: Sync Generated Sources
Graphaxe: Explain Project
Graphaxe: Export Generated XML
Graphaxe: Build Project
Graphaxe: Open Generated XML

How it resolves the tool

When src/graphaxe/tools/Run.hx exists in the current workspace, the extension prefers running the workspace checkout directly. That makes it convenient when you are developing Graphaxe itself.

Otherwise it falls back to the installed CLI:

haxelib run graphaxe

If you want a global graphaxe command outside VS Code, run:

haxelib run graphaxe setup

Requirements

VS Code 1.85 or newer
nadako.vshaxe
openfl.lime-vscode-extension
a Graphaxe project containing Graphaxe.hx or project.xml

The dependency extensions are declared in the manifest, so VS Code will prompt to install them automatically.

Workspace trust

Graphaxe shells out to local Haxe, Graphaxe, and Lime tooling. Because of that, it is intended for trusted workspaces only.

Workspace defaults

The Graphaxe repo itself also includes .vscode defaults so Ctrl+Shift+B and the main Graphaxe launch configuration go through the Graphaxe build flow instead of calling lime build project.xml directly.