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 🙏

© 2025 – Pkg Stats / Ryan Hefner

fairytale

v0.1.15

Published

It's a nice fairy tale.

Downloads

34

Readme

fairy tale

logo

It's a nice fairy tale.

Purpose:

  • Use it to exercise myself
  • Get a valuable and light blog engine

Start

Run

  • npm install fairytale -g to install.
  • fairytale -h to get the command usage.

Structure

| Name | Description | |:-------------:|:------------------------------------------------------------:| | Blog.yaml | The config file. | | Public | Any files you like. | | Root | The compiled files. | | Post | The posts. | | Theme | The templet. |

Blog.yaml defines some important varibles. The example is in CLI\blog\blog.yaml . Public directory will be copied to the root directory. Root directory saves deployed files.

Post

Post need to be placed in the Post directory, and the file must be named ".md". If your name of post file is "_", it will be ignored. Every post is composed of the content of Markdown with YAML front matter:

---
title: < title >
slug: < slug >
description: < description > # It's in front of the content.
date: < date > # It's the birth datetime by default.You must fill it in the right format.
category: < category > # It depends on your configs by default.
---
Content

Theme

Every theme is composed of 3 handlebars templates (post.hbs, page.hbs, category.hbs), 1 package file (package.json), and 2 directories (the "partials" and "assets"). All files of the "assets" directory will be copied to the "assets" directory under the "root" directory.

"package.json" describes the name and version of the Theme. You can also define some varibles by it. Its struct: { "name": "fairytale-theme-casper", "version": "0.1.1", "author": "longque", "variable": {} }

Handlebars provides the power necessary to let you build semantic templates effectively with no frustration.
To get more information, you can see http://handlebarsjs.com/ .

Fairytale provides some helpers: equal,encode,moment,downsize,text,foreach and more. To get more information, you can see my code :)

TODO

  • Complete the document
  • Provide the API
  • Rewrite it in plug-in architecture

Open Source

Git: https://github.com/longque/fairytale
LICENSE: The MIT License