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

@alstar/studio

v0.0.0-beta.20

Published

Alstar Studio is a **fullstack framework** for building CMS-driven applications with **native Node.js** and **Hono**.

Readme

Alstar Studio

Alstar Studio is a fullstack framework for building CMS-driven applications with native Node.js and Hono.

Installation

Create a new project:

pnpm create @alstar

Follow the CLI prompts to set up a starter project in your chosen folder.

Development

Start the dev server:

pnpm run dev

This runs a Hono server.

The core app is created via createStudio(structure), which returns the Hono app. This makes it possible to extend the server with plugins or custom settings:

const app = await createStudio(structure)
// app.use(...) custom middleware

Routing

Pages are defined in the /pages directory.

  • Each .ts file becomes a route.
  • Dynamic routes are created with square brackets, e.g. /pages/[slug].ts.

CMS

Access the CMS at:

/studio

Defining Content Structure

Pass a Structure object to createStudio(structure) to define the schema.

Use the helpers:

import {
  defineBlock,
  defineField,
  defineStructure,
  defineBlockField,
} from '@alstar/studio'

Example: Schema Definition

const titleField = defineField({
  label: 'Title',
  type: 'text' | 'image' | 'markdown' | 'slug',
  description: 'Page title',
})

const pageBuilder = defineBlockField({
  label: 'Sections',
  type: 'blocks',
  children: {
    hero: defineBlock({
      label: 'Hero',
      type: 'hero',
      fields: {
        /* fields */
      },
    }),
    gallery: defineBlock({
      label: 'Gallery',
      type: 'gallery',
      fields: {
        /* fields */
      },
    }),
  },
})

const entryBlock = defineBlock({
  label: 'Entry',
  type: 'entry',
  fields: {
    title: titleField,
    builder: pageBuilder,
  },
})

export default defineStructure({
  entry: entryBlock,
})

Concepts

  • Blocks contain fields.
  • Block fields (type: 'blocks') can nest multiple block types under children.
  • This enables page builders and reusable structures.

All content is stored in a SQLite database (studio.db) and can be queried in the templates with the query module.

Frontend

The framework encourages server-side rendering with Hono’s HTML helper (re-exported by the @alstar/studio package):

import { defineEntry, html } from '@alstar/studio'

export default defineEntry((c) => {
  const slug = c.req.param('slug')

  return html`
    <h1>Hello World</h1>
    <p>This page is: ${slug}</p>
  `
})

Interactivity

Even though the framework allows for having any library and tool for creating client-side behavior, it's recommended to use lightweight libraries such as:

Quickstart Example Project

This example shows how to define a simple page schema and render it on the frontend.

1. Define the CMS Schema (./index.ts)

import {
  createStudio,
  defineBlock,
  defineField,
  defineStructure,
} from '@alstar/studio'

const page = defineBlock({
  label: 'Page',
  type: 'page',
  fields: {
    title: defineField({
      label: 'Title',
      type: 'text',
    }),
    slug: defineField({
      label: 'Slug',
      type: 'slug',
    }),
    body: defineField({
      label: 'Body',
      type: 'markdown',
    }),
  },
})

const structure = defineStructure({
  page,
})

await createStudio(structure)

2. Create a Frontend Route (/pages/[slug].ts)

import { defineEntry, html, query } from '@alstar/studio'

export default defineEntry(c) => {
  const slug = c.req.param('slug')
  const page = query.root({ type: 'slug', value: slug })

  if (!page) return c.notFound()

  return html`
    <main>
      <h1>${page.fields.title.value}</h1>
      <article>${page.fields.body.value}</article>
    </main>
  `
}

3. Run the Project

pnpm run dev

Visit:

  • CMS admin: http://localhost:3000/studio
  • Frontend page: http://localhost:3000/my-first-page

Create a new page in the CMS, set its slug field to my-first-page, and the frontend will render it automatically.