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

create-octane

v0.0.9

Published

Create an Octane app: npm create octane my-app

Downloads

1,503

Readme

create-octane

Create an Octane app in a new directory.

npm create octane my-app
cd my-app
npm run dev

pnpm create octane my-app, yarn create octane my-app, and npx create-octane my-app all reach the same place.

Templates

You are asked which one you want, along with a project name, or you can say it up front:

npm create octane my-app -- --template spa
npm create octane my-app -- --template fullstack

npm needs that -- to forward the flag; pnpm and yarn forward it already, so drop it there.

spa is a client-only app: the compiler plugin, an index.html, and an entry that mounts one component.

index.html
vite.config.ts
tsconfig.json
package.json
.prettierrc
src/
  main.ts        mounts App into #root
  App.tsrx       the landing page
  styles.css     the reset and the theme tokens

fullstack adds octane.config.ts with routing, streaming SSR, hydration, and a production build, and it uses that surface rather than describing it: a second page, and an endpoint that returns a Response instead of a component.

index.html            carries the <!--ssr-head--> / <!--ssr-body--> markers
octane.config.ts      2 render routes + 1 server route
vite.config.ts
tsconfig.json
package.json
.prettierrc
src/
  App.tsrx            /
  Counter.tsrx        /counter — server-rendered, then hydrated
  Layout.tsrx         the frame both pages share
  styles.css          the reset and the theme tokens
  server/health.ts    GET /api/health

Both open on a page that links back into the documentation, and both are a working starting point rather than a directory of things to delete. The palette, typography and card styling are octanejs.dev's own, so a new app and the documentation look like one thing; src/styles.css holds the tokens and both colour schemes, and each component carries its own scoped <style>. There is no CSS framework to uninstall.

What it does

It runs octane create, which makes the directory and its package.json and then writes the TypeScript settings .tsrx needs, the bundler config, the scripts, and the entry files. That last part is the same code octane init runs against a project you already have, so the two cannot scaffold different projects.

This package is only the entry point. Everything above lives in @octanejs/cli, so npm create octane my-app and octane create my-app are the same command reached two ways.

Dependencies are installed through your package manager, which is also what records them in package.json. Pass --no-install to skip that, and the list to install by hand is printed instead.

Editor support

An Octane project builds, typechecks, and runs from the scaffold alone. Install TSRX Syntax for VS Code for syntax highlighting, diagnostics, navigation, completions, and TypeScript-aware editor support in .tsrx files. Pair it with the official Prettier extension for format on save. The scaffold's tsrx-tsc typecheck remains the command-line and CI check.