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

the-creature

v1.0.1

Published

_PHUUHIN ONNA RRRIIITZ_

Downloads

3

Readme

The Creature

PHUUHIN ONNA RRRIIITZ

What is this?

A guide and a list of tools to aimed at helping you make your own franken-site.

What do I do with it?

  1. Get Skeleton from the Skeleton Framework page.
  2. Run through the list of Bones and pick out the things you'll need.
  3. Put 'em together and make your own monster.

So this is a field guide for cobbling together various parts to make a cohesive site?

You got it.

Why?

The web is a gnarly, mixed up place to build things. The execution and rendering environments for our code are wildly inconsistent, given to a constantly shifting, heaving landscape. Data comes and goes like a breeze. The communities are volatile, ever changing. The tools, likewise.

As developers, we seek to make our lives easier by doing a bunch of redundant work up front so we can focus on the important stuff.

Doing that for the web is hard (see above). A handful of really successful projects have done it well, and have become huge in the process.

Mobile is more important every second, driven by the proliferation of more affordable, more powerful devices. Driven by increasing the sheer accessibility of the web. More people on the web is better for people and the web.

So we shift our focus. Huge can be a problem if you're targeting users on weak networks. Huge can result in slow, and huge can result in difficulty extending and maintaining.

Rather than one huge package, many small packages. Rather than everything included, only what's needed. This gets tricky too, though. Keeping things isolated and modular, reducing redundancy. The browser makes this hard.

Big framework or no, we end up creating franken-sites, mashing together various libraries and components in pursuit of getting things done.

We end up making The Creature.

Here, as an experiment, we'll collect a simple guide, some straightforward tools, and a list of small, quality components. This guide will server any who use it, but it'll be aimed at less experienced developers. It will seek to illustrate common practice and help people avoid pitfalls. It will provide a handy field guide to sourcing UI components and rolling them into your projects.