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 🙏

© 2024 – Pkg Stats / Ryan Hefner

bloguito

v0.3.1

Published

A very small blog engine.

Downloads

6

Readme

bloguito

Build Status

Bloguito is a really small blog engine.

some design constraints

here's a few of the design constraints I imposed on myself for this project:

  • no databases - this means the posts will be plain text files, written in markdown or some superset of markdown.
  • no technologies I am familiar with - this means ~~ruby~~ Node.js and nginx. and css. yes. I don't know css.

what's planned for the very first version

  • reading posts from a directory and showing them in a page

what's planned for the future

  • we'll see.

some history and motivation

I have to admit that the first purpose of this blog engine really is just to geek out a bit.

I wanted to learn ruby, I was suffering from not invented here syndrome, and I guess it's just not professional that your personal website is just an installation of wordpress or a blog on tumblr.

I also wanted to remove PHP from my server completelly :-|

Finally, my friend Pedro did something similar so I wanted to see if I could to it as well.

Except I wanted it even simpler.