Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>Eggplant Pattern PreviewNew to Visual Studio Code? Get it now.
Eggplant Pattern Preview

Eggplant Pattern Preview

MilkBlock

|
1 install
| (0) | Free
Live preview of cursor-scoped eggplant Rust patterns in VSCode.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Eggplant Pattern Preview

VSCode shell for the eggplant-pattern-extractor Rust CLI.

Current status

This first shell:

  • listens to Rust cursor/document changes
  • calls the local Rust extractor with the current cursor offset
  • converts PatternIR to DOT
  • forwards DOT to tintinweb.graphviz-interactive-preview

Development

Build and bundle the Rust extractor first:

cd ../eggplant-pattern-extractor
cargo build
cd ../eggplant-pattern-vscode
npm run bundle:extractor

Then compile the extension:

cd ../eggplant-pattern-vscode
npm install
npm run compile

Default repo-local validation paths:

npm test
npm run test:extension-host
  • npm test runs the headless-safe suite.
  • npm run test:extension-host runs extension-host validation without requiring a locally preinstalled Graphviz extension; the harness provisions the packaged dependency for the test profile.
  • npm run test:extension-host:graphviz enables the optional Graphviz smoke test.

For one-shot local packaging, use:

npm run package:extension

This builds the Rust extractor, copies the current platform binary into bin/<platform-arch>/, and compiles the TypeScript extension.

To create a local VSIX from the current platform build, use:

npm run package:vsix

For CI/release packaging, the repository includes .github/workflows/release-extension.yml. That workflow:

  • builds extractor binaries for darwin/linux/windows across x64/arm64
  • stages them into bin/<platform-arch>/
  • packages a single VSIX containing all supported native binaries
  • optionally publishes to the VSCode Marketplace when both VSCE_PAT secret and VSCE_PUBLISHER repo variable are configured

Marketplace notes:

  • package.json.publisher is still local for repo development
  • CI overrides it with VSCE_PUBLISHER before packaging/publishing
  • publish requires a Visual Studio Marketplace publisher plus a PAT with marketplace publish rights
  • the extension package now ships with a checked-in LICENSE; update it if you later decide to open-source the project
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft