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

gridplus-ui-components

v1.2.55

Published

A React component library, comprised of reusable components created to be shared across web projects at Grid+. By using this library we ensure design and brand consistency across platforms while minimizing code copypasta.

Downloads

5

Readme

ui-components

A React component library, comprised of reusable components created to be shared across web projects at Grid+. By using this library we ensure design and brand consistency across platforms while minimizing code copypasta.

Getting Started

Installing in your project

To install this project as a package in your web app, run:

npm i -S git+ssh://[email protected]/GridPlus/ui-components.git ui-components

By default, npm will install the latest tagged version of ui-components from git. From here you should be able to include any of the available components like so:

import { Button } from 'ui-components'

<Button label="click me" primary onClick={() => console.log('click')} />

To see full documentation, clone the repo, and run npm i && npm run start. This will run your tests, generate the documentation, and start up storybook.

Contributing

Please ensure all changes are made by the alpha branch. The reasoning for this is explained in the deployment section.

Updating current components

When updating components, ensure that the component is well documented, and has each of their propTypes listed. If you look at the current components, you will see their documentation format which you will want to copy. The comments for a component are used to automatically generate documentation which will be shown in Storybook. A comment above the component definition will be used as the description. Each of your declared propTypes will be added to a table within storybook, and the comments above each of your prop type definitions will be used as their descriptions.

Adding new components

To add a new component you will want to run the npm run new-comp ComponentName command in your terminal. This will do the following:

  1. Generate a folder in src/components directory with a .js file of the same name as well as an index.js file exporting the component.
  2. Export the component from src/components/index.js
  3. Add a folder to the /stories directory, which pulls in your component and displays it as a story.

Deployment

Once all your changes have been committed, deploying is very easy. When deploying we want to keep all branches and tags to be in sync. To do this, you have a simple command available to run using npm run release. This will prompt you to enter the type of change this is using semantic versioning; either major/minor/patch. Type in your version and hit enter. This will update the package.json version for you correctly, push your changes, jump over to master to do the same thing, and then jump back to alpha.