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

@syncropel/workspace-templates

v0.2.0

Published

Seven worked examples of `core.workspace.v1` manifests — tracker, multi-page, newsletter, course, recipe-collection, solo-tracker, and the multi-user code-review-pair. Each template ships with a workspace.json manifest, a README, and a fixtures/expected p

Readme

@syncropel/workspace-templates

Six worked examples of core.workspace.v1 manifests — each ready to scaffold via spl workspace init <name> --template <id> and tested against bundled fixtures with spl workspace test.

These are the same templates embedded in the spl binary at build time. This package mirrors them so the gallery is browsable on the web and downloadable without a Rust toolchain.

Templates

| id | Description | Components | |---|---|---| | tracker | Single-fold tracker (default) | One view | | multi-page | Linked pages workspace | Three pages: home, about, contact | | newsletter | Public-read broadcast workspace | One page + subscribe permission | | course | Course workspace | Syllabus, assignments, discussion, gradebook | | recipe-collection | Recipe collection | Index, featured, recently added | | solo-tracker | Personal tracker (per-user policy) | One view |

Browse the rendered gallery at docs.syncropel.com/templates.

Use a template

The canonical entry point is the CLI:

spl workspace init my-recipes --template recipe-collection
cd my-recipes
spl workspace test
spl workspace publish --draft

spl workspace init writes the template into a fresh directory, substituting __NAME__, __SLUG__, __DID__, and __DISPLAY_KIND__ placeholders. The result passes spl workspace test immediately.

Use a template directly

If you don't have spl installed yet, every template is a plain set of JSON + Markdown files you can copy from this package or from GitHub.

npm install @syncropel/workspace-templates
# Templates land at node_modules/@syncropel/workspace-templates/templates/

Or import the manifest list programmatically:

import {
  TEMPLATE_IDS,
  TEMPLATE_DESCRIPTIONS,
  type TemplateId,
} from "@syncropel/workspace-templates";

for (const id of TEMPLATE_IDS) {
  console.log(id, TEMPLATE_DESCRIPTIONS[id]);
}

Each template

Every template directory contains:

<template-id>/
├── workspace.json              # core.workspace.v1 manifest
├── README.md                   # what this template demonstrates
└── tests/
    ├── fixtures/basic.json     # input records
    └── expected/basic.fold.json # expected fold output

The workspace.json includes placeholder strings that spl workspace init substitutes at scaffold time:

| Placeholder | Substituted with | |---|---| | __NAME__ | The workspace name argument | | __SLUG__ | A URL-safe slug derived from name | | __DID__ | The current actor's DID | | __DISPLAY_KIND__ | The chosen display kind (default: workspace) |

Templates are validated against @syncropel/config@^0.7's core.workspace.v1 schema before scaffold.

See also

License

Apache-2.0. See LICENSE.