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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@minic-studio/appa-design-system

v3.0.1

Published

**Appa** is a web application in progress of development, created and designed by **Minic Studio**.

Readme

APPA - Design System

Appa is a web application in progress of development, created and designed by Minic Studio.

Currently finished design system elements can be found in this link.

Content

The design elements are grouped in three categories:

  1. Materials
  2. Components
  3. Organizations

1. Materials are the core elements, the 'atoms' of the design system. These are the colors, shadows, line heights and font weights used through the project.

2. Components are a variety of small building blocks with different use case options. We also call them 'molecules'.

3. Organizations are bigger modules used through the application that contains multiple pieces of components. These modules may have some kind of functionality added to them, available to test in the design system.

Installation

Download or clone the code from the develop branch. Install all the dependencies:


npm install

This may take a few minutes...

After it's done, you can run the storybook of all the elements created:


npm run storybook

If You would like to create standalone version of the storybook then:


npm run build-storybook

Development

Anytime your pull request is accepted by a superior the new content created is pushed into the develop branch. This is the main branch used by developers. If you are ready to publish the newer version of the design system, you have to check a few things before.

  • Ask for collaborator role! Since the npm package is scoped, which means it is hidden from the public, only collaborators can publish changes.
  • Test the package locally! You can test your package with a simple CRA project and see if the imported components behave as it is awaited. - Create a react app in the same folder where the design-system was placed - Run npm pack ../design-system to create a locally usable npm package - Install the freshly packed .tgz file with npm i [filename].tgz, which now can be found inside your node_modules
  • Edit version number! Inside the package.json file in the main directory, you must edit the version number consistently. - Find the "version": "x.x.xx" in the second line - If you made major changes, than edit the first x. If you made minor changes, then edit the second x, else as a patch edit, you have to edit the last one or two x's - For more information about these specifications, read the Semantic versioning documentation.
  • Check import / exports! Inside the src/components/ directory you can find the index.js. This file is responsible to collect all the components then export them for further use. If you have created a new component, please do not forget to import then export!

Publishing

If you are ready to publish your changes, first, you have to login with your npm credentials. Open the terminal from the design-system folder and type npm whoami, to check your login status. If you are not logged in then you must type npm login and followed by instructions, type your information.

Run npm run compile in the terminal to create the compatible build of your code.

Finally with npm publish you are ready to go!