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

clever-components

v2.224.0

Published

A library of helpful React components and less styles

Downloads

758

Readme

Clever Design System

Check out documentation and live examples for Dewey, as well as our getting starting guide.

Development

Adding a new component

The following command will create a new component shell in src/MyNewComponent/ along with a starter test file and demo boilerplate:

./bin/new_component.sh MyNewComponent

You can also create additional sub-components in any existing directory by running:

./bin/new_sub_component.sh MyNewSubComponent ./src/MyNewComponent

You can then modify the component and demo code as needed. Your new component can be viewed at http://localhost:5010/#/components/my-new-component while the demo server is running.

Component List

After creating a new component, make sure to add it to the Component List in ComponentsView.jsx. To do so:

  • Add an entry in ComponentsView.componentsToDisplay using this template:
    {
      componentLink: "<COMPONENT LINK>",
      componentImg: "<COMPONENT LINK>.png",
      componentName: "<COMPONENT NAME>",
      componentImgAlt: "A <COMPONENT NAME> component",
    },
  • Add a screenshot of the component in docs/assets/img with the format <COMPONENT LINK>.png

Adding new SVGs

We use SVGs as JSX components for Icons, following this process:

  1. Optimize the svg at svgomg
  2. Make it React compatible with double quotes option at svg2jsx
  3. Prefix DOM Ids and classnames with component name if necessary
  4. Add it to the code:
    • Create a new file in src/Icon/icons/<<NewIcon>>.jsx
    • Add to src/Icon/icons/index.jsx and src/Icon/Icon.jsx

Running the demo server locally

Start up the demo server by running

make dev-server

Testing locally on a repo that uses these components

For Clever engs, refer to this doc on how to test your changes in the context of other apps.

In short, if you want to test changes you've made to this repo in the context of another repo that uses clever-components, run the components repo's make build command and use the freshly generated dist directory in replacement of the clever-components/dist directory on your other project's repository.