Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>Poly BenchNew to Visual Studio Code? Get it now.
Poly Bench

Poly Bench

evm-tools

|
1 install
| (0) | Free
Language support for .bench files with embedded Go, TypeScript, and Rust - powered by poly-bench LSP
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

poly-bench VS Code / Cursor extension

Adds syntax highlighting for .bench files:

  • DSL: suite, setup, fixture, bench, description, iterations, warmup, hex, and # comments
  • Embedded Go: Code inside setup go { ... } is highlighted as Go
  • Embedded TypeScript: Code inside setup ts { ... } is highlighted as TypeScript

Install (development)

  1. Open the extensions/vscode folder in VS Code or Cursor.
  2. Press F5 (or Run > Start Debugging) to launch a new window with the extension loaded.
  3. Open a .bench file to see highlighting.

Install (from repo)

  1. In VS Code/Cursor: Extensions → ... → Install from VSIX (if you built one).
  2. Or copy the extensions/vscode folder into your workspace and use Developer: Install Extension from Location with the extensions/vscode path.

Publishing to the Marketplace

  1. Create a publisher (one-time): Go to Visual Studio Marketplace - Publishers and sign in with Microsoft/GitHub. Create a new publisher; use the same id as publisher in package.json (e.g. poly-bench).

  2. Install the publishing tool:

    npm install -g @vscode/vsce
    
  3. Build and package (from the extensions/vscode folder):

    npm run compile
    vsce package
    

    This creates poly-bench-0.0.1.vsix.

  4. Publish (requires a Personal Access Token with Marketplace (Publish) scope):

    • Create a PAT at Azure DevOps → User settings → Personal access tokens with Marketplace (Publish) scope.
    • Run:
    vsce login poly-bench
    # enter the PAT when prompted
    vsce publish
    

    Or bump version and publish: vsce publish patch (0.0.1 → 0.0.2).

  5. Install from VSIX (without publishing): Use the .vsix from step 3: in VS Code, Extensions → ... → Install from VSIX... and select the file.

Formatting notes

  • Suite closing brace: The } that closes the top-level suite block should be at column 0 (no leading spaces). This avoids the grammar ending the suite at an inner }.
  • Setup closing brace: setup go { } and setup ts { } end at a } on its own line with 2–4 leading spaces. Use consistent 2- or 4-space indent for the block body so the first such } is the setup closer.
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft