Skip to content
nexisv1.3.3Build with Nexis
← All documentation

Reference · guide 21

Contributing to Nexis

Package selection, code style, test expectations, documentation, benchmarks, commits, review, and responsible security reporting.

HTML-first routestatic reference pagev1.3.3 checked

01

Change the smallest owning package

Locate the exact package responsible for the behavior before editing. Keep public API, runtime, compiler, adapter, and documentation changes scoped and coherent.

02

Tests document compatibility

Add or update focused tests for route output, compiler diagnostics, runtime behavior, adapters, and public type declarations whenever a contract changes.

03

Protect users and maintainers

Keep commits focused, document compatibility changes, avoid credentials, and report vulnerabilities through the security process rather than public exploit detail.

PRACTICAL LABS

Run this capability.

Each example states the observable output, the boundary that remains your responsibility, and the check that proves the result.

01

Change one owning package

Shell
pnpm --filter @mohammedaydan/router test
pnpm format:check
pnpm check
pnpm release:check
OUTPUT
A change has focused proof before the complete workspace gate.
BOUNDARY
A documentation change must not advertise behavior that its test or public declaration does not support.
PROVE IT
Review code, tests, docs, generated output, and compatibility together.

VERIFICATION

Prove the contract.

Run the relevant package and integration checks, format/typecheck gates, git diff checks, and review the generated documentation before opening a pull request.