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

ui-puppy

v0.4.9

Published

A ReactJS UI library inspired by Eva Design

Downloads

162

Readme

UI Puppy 🐶

A ReactJS UI library inspired by Eva Design

View stories: https://plantjammerdk.github.io/ui-puppy

Contribute

Continuous integration (Github Actions)

Whenever you push, Github Actions will run. We have one called chromatic, that checks for visual regressions using the Storybook stories. So stories === tests. And one called release that make a release on npm. Only pushes to master, i.e., pull requests, will create "real" npm releases. So when you simply push your branch, it will create a so-called canary release, that can still be installed, but it will be clear that it's not an official release.

If you want to skip these actions, add skip ci to your commit message.

Styling

The project uses TailwindCSS. In order to get the most out of this library, please follow these guidelines:

  1. Strive to only use the utility classes in Tailwind - no custom classes or css files. Using the style prop is fine.
  2. Try to limit colors to built-in colors such as bg-gray-100 and the extended colors in tailwind.config.js. This allows consumers to overwrite the colors to use for their theme. If we use hex codes or add more custom colors, they won't be customizable and custom colors won't even work, because they are local to this project.

Creating a component

  1. Create your component in the src/MyComponent.tsx folder.
  2. Create a MyComponent.stories.tsx file in the stories folder.
  3. Develop and test it using yarn storybook.

Playing around

If you want just want to locally test your work, you can yarn add from a local repo, e.g.: yarn add /Users/andersravn/plantjammer/ui-puppy.

Submitting/deploying

  1. When you are ready submit a pull request.
  2. Add labels to the pull request, particularly patch/minor/major. These are used by the Auto package to bump the version automatically.

If you want to test if it will build the package, run yarn build.

TODO

  • [x] Automatic deployment when merging pull requests
  • [X] Chromatic tests
  • [x] CI

Library setup

The library is set up as a combination of these two guides:

https://www.pluralsight.com/guides/react-typescript-module-create

https://www.learnstorybook.com/design-systems-for-developers/react/en/distribute/