Contributing

Pre-Release

Verter is pre-release software. APIs may change between releases — see the API Stability document.

How to contribute to Verter.

Prerequisites

• Node.js 18+ and pnpm 9+
• rustup — rust-toolchain.toml pins the exact compiler plus rustfmt, clippy, and the wasm32-unknown-unknown target, and rustup installs all of them on your first cargo invocation in the repo. Install cargo-nextest separately.
• VS Code (for extension development)

Setup

git clone https://github.com/pikax/verter.git
cd verter
pnpm install
pnpm build

pnpm build runs sequentially: native bindings, LSP binary, WASM, then TypeScript packages. This ensures all downstream consumers have their dependencies available.

Development

pnpm watch            # Watch-build TS packages for extension development
pnpm dev-extension    # Build LSP binary, then watch language-shared + extension + TypeScript plugin

To test the extension locally, press F5 in VS Code after building to launch the Extension Development Host.

Testing

# TypeScript / JavaScript
pnpm test                                      # Every package-owned test script
pnpm --filter @verter/typescript-plugin test  # One package
pnpm exec vitest run path/to/test.ts           # One test file

# Rust
node scripts/gate.mjs                      # Provider-free core Rust gate
node scripts/compile-contracts.mjs         # Standalone compile contracts
cargo test -p verter_compiler test_name    # Targeted iteration

See the Testing Guide for detailed testing patterns and requirements.

Code Style

Run these checks after making changes:

cargo clippy --workspace -- -D warnings
cargo check --workspace --release                                            # release-only compile errors
cargo clippy --target wasm32-unknown-unknown -p verter_wasm -- -D warnings   # target-gated code
cargo fmt --all --check

The last two cover build configurations no other local check compiles: host clippy builds debug only and cannot see #[cfg(target_arch = "wasm32")] code at all. CI runs both in the rust-build-configs job.

TypeScript formatting follows the project's existing style. There is no separate formatter command -- maintain consistency with surrounding code.

Commit Convention

This project uses conventional commits for automatic changelog generation via git-cliff:

<type>(<scope>): <description>

Types

Type	Description
feat	New feature
fix	Bug fix
perf	Performance improvement
refactor	Code refactoring (no behavior change)
docs	Documentation only
test	Adding or updating tests
chore	Build, CI, or tooling changes
release	Version bump and release

Scopes

Scope	Area
compiler	verter_compiler Rust crate
napi	verter_napi / @verter/native
wasm	verter_wasm / @verter/wasm
play	Playground
unplugin	@verter/unplugin
lsp	Language server
types	@verter/types
ci	CI/CD workflows
*	Multiple areas

Examples

feat(compiler): add v-memo directive support
fix(lsp): correct hover position for multi-line expressions
perf(core): batch mutation passes in template codegen
refactor(session): simplify semantic query ownership
docs: update contributing guide
test(compiler): add v-for key validation tests
chore(ci): add nightly WASM build workflow
release(all): v0.0.1-beta.1

Repository Structure

crates/          # Rust crates (compiler, semantic/session, LSP, FFI)
packages/        # TypeScript adapters, types, integrations, and clients
scripts/         # CI/CD and utility scripts
docs/            # Documentation (VitePress)

See the Rust Setup guide for details on the Rust crate structure.

PR Checklist

Before submitting a pull request:

• [ ] Tests added or updated covering the change
• [ ] Documentation updated if applicable
• [ ] No TypeScript errors (pnpm build:ts succeeds)
• [ ] Rust checks pass (node scripts/gate.mjs, node scripts/compile-contracts.mjs, cargo fmt --all --check, and warning-denied Clippy where applicable)
• [ ] Code style is consistent with surrounding code
• [ ] Conventional commit message used
• [ ] Both positive and negative assertions in tests (see Testing Guide)