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

callete

v1.0.12

Published

CLI for the Callete Framework.

Readme

Callete

A framework built for beginners, and speed.

Discord: discord.gg/SMP5Sy

Installing

Run this command:

$ npm i -g callete

to install callete.

Starting a project

callete create <name> [starter]

name: The name of the project

starter: A link to a git repository to clone

Development builds

callete build

Builds and runs a server.

Production builds

callete build -p [-N]

Builds a production-ready site in a dist folder in your project folder.

-N or --netlify: Builds for netlify with files like _redirects

Routing

In your callete project which has a very simple file structure:

callete.config.json  /components  package.json  routes.json

Where would we manage routes?

Yes, another amazingly simple feature of callete: routes.json

This is the default:

[
	{
		"url": "/",
		"component": "index.ette"
	},
	{
		"url": "/about",
		"component": "about.ette"
	}
]

No need to be scared! It's just a JSON array. Just make another object in the array, like if we wanted a contact page:

[
	{
		"url": "/",
		"component": "index.ette"
	},
	{
		"url": "/about",
		"component": "about.ette"
	},
	{
		"url": "/contact",
		"component": "contact.ette"
	}
]

Now the other important piece of the puzzle where are we linking to in the component variable?

Well we just link to a file in the components folder.

.ette

The .ette extension is calletes form of html its literally html with custom components its just a filename extension no need to be worried.

Components

The simplest yet most effective part of callete!

As simple as this:

components/index.ette

<Navigation>

Now how would we make a component

components/Navigation.ette

<a href="/">Home Page</a>
<a href="/about">About Page</a>

Yes, as simple as that.

Markdown

To include markdown into your pages you need to create a markdown directory.

We'll be calling it Markdown.

No subdirectory support is currently included for your markdown folder.

Now you have to edit your callete.config.json.

The default is this:

{
	"name": "<name>",
	"description": "A Callete App.",
	"version": "1.0.0"
}

To add markdown:

{
	"name": "Docs",
	"description": "A Callete App.",
	"version": "1.0.0",
	"markdown": "Markdown"
}

Then to include it in any of our .ette files:

<Markdown file='filename (no .md)'></Markdown>