npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@axiomvn/create

v0.3.0

Published

Create a ready-to-run Axiom VN project.

Readme

@axiomvn/create

The scaffolder for Axiom VN. It is how a project starts.

npm create @axiomvn my-game

That writes a small finished story — a lamp above a cliff, and whether it gets lit — with its story file, its configuration, its assets, its page, and its build already wired together. The generated project's own README.md explains every file it created and is the guide to working in it; you can read it before scaffolding, which ships in this package at node_modules/@axiomvn/create/template/README.md and is copied into the project the scaffolder writes.

A scaffolded project also carries AGENTS.md for coding agents, which ships here at node_modules/@axiomvn/create/template/AGENTS.md. It is a map rather than a second guide: where the story language is defined in the installed packages, which commands the project defines, the validation loop to run after every edit, and what the runtime derives that an author must not write by hand.

It is a copier, not a generator

This package depends on no engine package. It never constructs a pack, never imports the content boundary, and does not know what a node is: it copies a directory and rewrites two fields of a manifest. The day it needs to understand a story is the day something has gone wrong, because a scaffolder that understands stories is a second authoring surface competing with the real ones.

There is no template language, no conditional file emission, and no framework choice — the template is a directory a person can read and run. The engine versions it writes are its own, read from this package's manifest, so a scaffolded project pins a set of packages that were typechecked together.