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

@stone-js/starters

v0.8.19

Published

This repository contains official **starter templates** for Stone.js applications.

Readme

Stone.js - Starters

License: MIT Maintenance Used by Stone CLI

This repository contains official starter templates for Stone.js applications.


Overview

It is used internally by the Stone CLI to generate scaffolded projects for both microservices and frontend React apps, with three predefined levels of complexity: basic, standard, and full.

Available Starters

Each starter reflects a different level of complexity and domain (microservice or React), with both declarative and imperative styles available. You can pick the one that matches your architecture preferences and scale needs.

Microservice Starters

| Name | Description | | ------------------------------ | ------------------------------------------------------------------ | | basic-service-declarative | Minimal Stone.js microservice using class and decorators | | basic-service-imperative | Minimal functional microservice with handler and blueprint | | standard-service-declarative | Adds routing, DI, and hooks with a clean declarative structure | | standard-service-imperative | Functional routing setup with middleware and service container | | full-service-declarative | Production-grade setup: lifecycle hooks, DI, error handling, tests | | full-service-imperative | Complete functional microservice with config, tests, and events |

React App Starters

| Name | Description | | ---------------------------- | ------------------------------------------------------------------------ | | basic-react-declarative | Minimal React + Stone.js (SPA/SSR-ready) using class-based API | | basic-react-imperative | Minimal React app using functional API and manual config | | standard-react-declarative | Adds layout, routing, and lifecycle via decorators | | standard-react-imperative | Function-based setup with routing, layout system, and render control | | full-react-declarative | Enterprise-ready app with head config, hydration, and complete structure | | full-react-imperative | Full functional React app with SSR, hooks, tests, and platform config |

You can combine complexity level (basic, standard, full), domain (react, service), and style (declarative, imperative) to find the right starter, for example: standard-react-imperative.

How It's Used

These starters are not meant to be installed manually.

Instead, the @stone-js/cli automatically pulls from this repository during:

npm create @stone-js

or

stone init

The CLI fetches the appropriate template based on user choices and sets up a ready-to-run project in seconds.

Starter Structure

Each starter is a self-contained folder containing:

  • app/, asset/, public/, tests/ depending on the type
  • Minimal stone.config.mjs or framework config
  • Preset integration (e.g. adapters, blueprint, lifecycle)
  • Preconfigured TypeScript + Vitest (for standard/full)
  • Working example of event handler or route

Maintaining the Starters

To update or add a new starter:

  1. Fork or clone this repository.
  2. Add or modify the corresponding folder (e.g., react-full, micro-basic).
  3. Keep external dependencies minimal.
  4. Test the template using the CLI locally.
  5. Submit a PR following the Contributing Guide.

The Stone CLI will always fetch the latest main branch when scaffolding.

Why Three Levels?

Stone.js follows a progressive complexity approach. These templates help developers grow their app without needing to eject or reconfigure from scratch.

  • Basic: Hello world in 10 seconds.
  • Standard: Real-world app features with good defaults.
  • Full: Production-grade architecture with opinions.

Learn More

This package is part of the Stone.js ecosystem, a modern JavaScript framework built around the Continuum Architecture.

Explore the full documentation: https://stonejs.dev

Contributing

See Contributing Guide