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

@saleshandy/design-system

v0.17.4

Published

Saleshandy Design System

Downloads

298

Readme

Saleshandy Design System

A Design System is the single source of truth which groups all the elements that will allow the teams to design, realize and develop a product.

🚀 Setting up the project

1️⃣   Install required dependencies →

npm install

2️⃣   Run the compiler in watch mode, it watches for changes and auto compiles the code →

npm start

3️⃣   Run the Storybook preview, it opens up the preview in browser at http://localhost:6006 →

npm run storybook

4️⃣   Create project build, it compiles and generates static code in dist folder with minified js and css for production →

npm run build

5️⃣   Create storybook build, it compiles and generates static storybook preview for deployment in storybook-static folder →

npm run build-storybook

⭐ Steps to add component in design system

1️⃣   Create folder with component name (sample folder structure shown below)

2️⃣   Define the component jsx, filename will be component-name.tsx

3️⃣   Add styling to the component by creating a file with name, _component-name.scss in the assets/scss directory and import it in design-system.scss file with a help comment (as shown below)

// Component-Name Styles
@import './scss/component-name';

4️⃣   Create an index.tsx entry file for component export

5️⃣   Write the documentaion by creating a story file in the stories folder, filename will be component-name.stories.tsx

📁 Sample Component Folder Structure →


├── src
│   ├── button                  → folder with component name
|   │   ├── button.spec.tsx     → component unit test file
|   │   ├── button.tsx          → component jsx file
|   |   └── index.ts            → component export index
|   │
|   ├── assets
|   |   ├── scss
|   |   |   └── components
|   |   |       └── _button.scss    → component styling file (optional)
|   |   └── design.system.scss  → import component scss in this file
|   |
│   └── index.ts                → import component jsx in this file
│
└── stories
    └── button.stories.tsx      → component documentation in storybook

🔗 Conventional Commits Referrence Docs

Read more about conventional commit here