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

floorplan

v0.0.1

Published

The place to start for making a component library.

Downloads

5

Readme

floorplan-base

The place to start for making a component library.

Hi!

This repo is a starting place for a component library. Simply clone this and add what you want.

Dependancies

The dependancies are add completely based on opinion. There are other ways to accomplish this but, these are some of the more popular tools in the industry. The main goal here is that if you run into problems you hopefully wont be the first one and can google for an answer.

What's in here?

In here you will see the dev build tools and dev tools. You will not see frame works like React, Angular, Vue, etc. You also wont see css frame work decisions here. This allows every one to start here and make choices like that based on their opinions. It is recommended to use storybook for the testing environment but it is not necessary, and therefore not included at this stage.

Philosophy

Everything in here is based on atomic design. The component library will only consist of atoms, molecules and organisms. Anything beyond that in atomic design is contextual and does really belong here. These these begin to be to related to implementation and not really sharable. Think about it this way, if you were to open source your library would it make sense for you to share all the pieces in there. The moment you identify pieces that don't make sense you should find a place for them else where.