@axiomvn/toolchain

How an Axiom VN project is loaded, compiled, checked, and edited.

One loader reads a project — its axiomvn.config.ts, the .story files that config names, and the trusted TypeScript it composes from — and the development server, the production build, and the command line all use it, so a story that plays is the same story the commands agree with.

A scaffolded project installs this package as a development dependency. What it deploys is the compiled pack and no compiler.

Entry points

• @axiomvn/toolchain — project loading and analysis for a Node program.
• @axiomvn/toolchain/vite — the Vite plugin, which is where the bundler is reachable and nowhere else. It serves the compiled pack as virtual:axiomvn/pack and reloads an edited story without losing the reader's place.
• axiomvn — the command:

axiomvn validate [project]         # compile and validate, with no browser
axiomvn coverage [project]         # every path a reader can reach
axiomvn consistency [project]      # the story checked against itself
axiomvn language-server            # LSP on stdin and stdout, for any editor or agent

coverage and consistency need @axiomvn/testing, which this package names as an optional peer — a requirement those two commands make of a project rather than an edge the engine runs on.

Depends on @axiomvn/content, @axiomvn/language, and @axiomvn/persistence.

Start a project with @axiomvn/create.