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

labkit

v1.4.1

Published

## Intentions

Downloads

458

Readme

LabKit

Build Status

Intentions

LabKit is a component library: a set of reusable components that complement each other.

Documentation

Run make up and go to localhost:8081/labkit to see the documentation pages for labkit components.

When you change or add a component, remember to update the documentation to demonstrate the new feature.

Rules

These rules are general guidelines, not concrete. If in the future we decide that they're not a good idea we shouldn't be afraid of breaking or changing them.

  • There should be no global CSS helper classes, only SASS variables.

A component belongs in LabKit when:

  • It does not contain any application specific code.

    • For example, it should not call an API route and then insert the data into the store.
  • It does not rely on any state or data beyond props that can be passed in to the component.

    • It should not access the store directly.
  • It is generic.

TODO

  • How to add a new component
    • Setting up a page with examples.
    • Setting up the router.