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

zade-design-system-react

v1.0.5

Published

React component library | ZADE

Downloads

1

Readme

ZADE DESIGN SYSTEM

This is a Zade Design System – comprehensive collection of reusable components, styles, and guidelines designed to help you build consistent, accessible, and high-quality user interfaces with React.

Content

Features

  • React library;
  • TypeScript: A strongly typed superset of JavaScript;
  • SCSS: CSS preprocessor;
  • Storybook: A frontend workshop for building UI components and pages in isolation;
  • Vite: A next generation frontend tooling that runs and builds your library incredibly fast;
  • ESLint: A tool that finds and fixes problems in your code;
  • Prettier: A code formatter;
  • Husky: A pre-commit, pre-push hook;
  • Commitlint: Commit message conventions;
  • Surge: Auto deploy when pushing changes;
  • pnpm: Fast, disk space efficient package manager;
  • NPM package: A library that published in npm registry.

Getting Started

  1. Clone this repository;
  2. Install pnpm using npm install -g pnpm;
  3. Install dependencies pnpm i;
  4. Start project: pnpm dev.

Scripts

An explanation of the package.json scripts.

| Command | Description | | ----------- | ---------------------------------------------------------------------------------- | | dev | Starts the local Storybook server, use this to develop and preview your components | | build | Builds your Storybook as a static web application | | build:lib | Builds your component library with Vite | | lint | Runs ESLint tool | | format | Formats your code with Prettier | | prepare | Installs Husky, a tool for setting up Git hooks |

Contribution | Add feature/fix/improvement

  1. Create a Branch git checkout -b feature/your-feature-name;
  2. Optional, if you want to update npm package: Upgrade npm version with npm version {patch/minor/major};
  3. Commit your changes with convential commit. For example: git commit -m "feat(header): added new component";
  4. Push new branch git push origin feature/your-feature-name;
  5. Create Merge Request or merge with main branch immediately;
  6. Optional: Build project pnpm build:lib and call npm publish to upload dist directory in NPM.

Storybook deploy

There are two ways to get deployed version:

First:

  1. Build storybook via pnpm build:storybook;
  2. Go to the build folder cd storybook-static;
  3. Deploy with surge: npx surge (press enter twice);
  4. Go to the link in console to see deploy.

Second: When you push changes to the main branch, pre-push husky hook will auto deploy app with new changes to the deployed Storybook link.

NPM | Publish new version

Requirements:

  1. Build your lib via Vite: pnpm build:lib;
  2. Publish new version: npm publish.

Commit conventions

An explanation of the available commit conventions, more details you can find here.

| Command | Description | | ---------- | ------------------------------------------------------------------------------------------------------ | | feat | Commits, that adds or remove a new feature | | fix | Commits, that fixes a bug | | refactor | Commits, that rewrite/restructure your code, however does not change any API behaviour | | perf | Commits are special refactor commits, that improve performance | | style | Commits, that do not affect the meaning (white-space, formatting, missing semi-colons, etc) | | test | Commits, that add missing tests or correcting existing tests | | docs | Commits, that affect documentation only | | build | Commits, that affect build components like build tool, ci pipeline, dependencies, project version, ... | | chore | Miscellaneous commits e.g. modifying .gitignore |

Support

If you encounter any issues or have questions, please reach out to our support team:

Emails:
[email protected];
[email protected];
[email protected].

Bugs, improvements? Issues board.

Links: