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

smartbear-design-system

v0.1.0

Published

Presentational components implementing the SmartBear Design System

Downloads

3

Readme

SmartBear Design System

This repository contains presentational components implementing the SmartBear Design System.

See a live demo based on StoryBook.

Currently the only implementation is based on React, using Styled Components, and only a few components are implemented.

If people want to implement components using other UI technologies such as Vue, Ember or other we could move the React implementation to a sub directory.

We could also consider replacing Styled Components with a general-purpose CSS preprocessor and CSS Modules so that the same stylesheets can be used with several UI technologies.

Suggestions and pull requests welcome!

Try it out

# Install dependencies
npm install

# View components in Storybook
npm run storybook

# Run tests
npm test

Deploy live demo

Run this:

npm run deploy-storybook

TODO: Set up CI and run this automatically

Architecture

The design system is based on tailwindcss and tailwindui. This is extended with a custom theme and custom CSS classes.

Custom theme

The design system theme is implemented by extending tailwindcss' default theme, as described in Customizing Your Design System.

The theme defines the following values:

  • Colours (using design system specific names)
  • Spacing (padding, margin, width and height)

The theme is defined in tailwind.config.js. All names in the theme use the sb- prefix to distinguish from default tailwindcss names.

Defining Components

We define components in CSS according to tailwindcss' Extracting CSS components with @apply guidelines.

Upgrading Dependencies

It's good practice to regularly upgrade dependencies:

npx npm-check-updates --upgrade

After doing this, export the default tailwind config

npx tailwind init tailwind-full.config.js --full

This file is not in source control (it's in .gitignore), but it's useful to look at it to see if the structure has changed, in which case you may have to update the theme in tailwind.config.js

Releasing

npm version [major|minor|patch]
npm publish