Tooling

Norm's formatter, diagnostics, and editor features read the same semantic snapshot as the compiler. Type checking, name resolution, and project boundaries are implemented once.

Current capabilities

• Formatting and compiler diagnostics;
• Completion driven by scope and expected type;
• Signature Help and Hover;
• Go to Definition and Find References;
• Prepare Rename and semantic Rename;
• Navigation across files, packages, and standard-library sources;
• Project analysis including unsaved documents.

Structured API documentation reuses the same semantic entry point; see API Documentation Export. See Application Builds for self-contained application output conventions.

Start with examples

With the development toolchain, run norm hello in an empty directory to create five independent .norm programs and English and Chinese guides. Start with norm hell.norm, then follow the generated example guide.

norm run main.norm hides startup preparation logs by default. norm run --debug main.norm writes startup phases, elapsed time, and actual Maven downloads to stderr. Error diagnostics always appear; this option does not affect application output. See RunCommand for progress and JarResolverTest for the network boundary of local dependencies.

VS Code

For AI Agent navigation through specifications, queries, and validation, see Agent Development.

The official VSIX bundles a same-version self-contained CLI for supported platforms. See VS Code Development Experience for installation, execution, project detection, and CLI selection; see the release process for publication assets and platform matrix.

Shared semantic entry point

Source files
  → Project source set
  → Semantic model
  → diagnostics / completion / signatures
  → hover / navigation / references / rename
  → formatter / compiler

See Status for the currently delivered tooling boundary. A debugger and online execution environment are not yet in a release.