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

teaglass

v0.0.54

Published

A small static site builder

Downloads

7

Readme

##Installing glass

$ npm install teaglass -g

##glass Start new project

$ glass init

Build Project - it will update site folder with the new build.

$ glass render

##default.json With this file you can set the position of files and set any global variable.

{
    "theme": "templates", //theme folder
    "name": "", //name of the Site
    "title": "", //title of the site.
    "base": "", //base url from project
    "only": "" //can be an array or a string only this files will be rendered,
    "positions": [], //set prosition of files which come first and which come at last.
    "variables": {} //set xml variables such as <icon> and get the value setted as an variable on the templating system.
}

##Positions example

 {
 	"positions": ["index.md", "about.md", "how.md"]
 }

The first element rendered it will be index.md after that about.md and so on... The {{position}} object on template it will be 0 for index.md and 1 for about.md and at last 2 for how.md.

##Variables example

 {
 	"variables": {
    	"h1": "title"
    }
 }

The <h1> element it will be saved as a variable {{title}} on the templating system. Remember the <h1> element it will be removed from the markdown file.

##Templating All variables from default.json can be accessed by site object over the template.

###Example

<title>{{site.name}} - {{site.title}}</title>

###All objects:

{{content}} <!-- get content from markdown -->
{{site}} <!-- get object from default.json -->
{{position}} <!-- get position from rendering example if index.md it's the first to be rendered the position will be 0 -->
{{list}} <!-- it will return an array with all markdown files precompiled in html. -->