Syntax highlighting and language support for MX Script (.mx files).

Features

Syntax highlighting for keywords, strings (with ${...} interpolation), routes, operators, comments
Bracket auto-closing and surrounding
Block-aware indentation
File icon association for .mx

Install

Via VS Code Marketplace (once published)

ext install jlkdevelop.mxscript

Or search "MX Script" in the Extensions panel.

Via prebuilt .vsix (works today)

Each mxscript release ships a .vsix asset:

curl -fsSL -o mx.vsix \
  https://github.com/jlkdevelop/mxscript/releases/latest/download/mxscript-0.5.0.vsix
code --install-extension mx.vsix

Restart VS Code, open any .mx file, and highlighting kicks in.

From source

git clone https://github.com/jlkdevelop/mxscript.git
cd mxscript/extras/vscode
code --install-extension .

Publishing to the Marketplace (maintainers)

The first publish needs a one-time Azure DevOps setup; after that, every release is one command.

One-time setup

Sign in (or sign up) at dev.azure.com with the GitHub account you want to publish under.
Create a Personal Access Token:
- Click your profile avatar → Personal access tokens → New Token
- Organization: All accessible organizations
- Scopes: Marketplace → Manage
- Copy the token (you won't see it again).
Create the publisher and authenticate vsce:
```
npx @vscode/vsce login jlkdevelop
```
Paste the token when prompted. The jlkdevelop publisher matches package.json's publisher field.

Each release

From this directory:

npx @vscode/vsce package      # creates .vsix locally
npx @vscode/vsce publish      # uploads to Marketplace

Or in one shot when bumping the version:

npx @vscode/vsce publish patch   # 0.5.0 → 0.5.1
npx @vscode/vsce publish minor   # 0.5.0 → 0.6.0
npx @vscode/vsce publish major   # 0.5.0 → 1.0.0

Contributing

The grammar lives in syntaxes/mxscript.tmLanguage.json. It's a standard TextMate grammar — every editor that speaks TextMate (Sublime, Zed, Atom, etc.) can use it directly.