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

@fabrigeas/react-components

v2.0.7

Published

Contains some useful react components like Button, Input

Downloads

2

Readme

React components

A collection of often used react components

Try out

1 CodeSandbox

One way to try these components without installing them locally is running the codesandbox payground

Codesandbox

2- Locally

The other way by cloning the library and running the storybook locally

https:#github.com/fabrigeas/react-components
cd @fabrigeas/react-components
npm run start

# or (both scripts do the samething)
npm run storybook

Usage

1. Button

npm i @fabrigeas/react-components
import { Button } from '@fabrigeas/react-components';

# params:
# all react button params plus the following:
# outlined: boolean
# buttonType: 'info' | 'success' | 'warning' | 'danger'
<Button onClick={} type='submit'>Hello</Button> 
<Button outlined>Hello</Button>
<Button buttonType='success'>Save</Button>
<Button buttonType='info'>Start</Button>
<Button outlined buttonType='success'>Save changes</Button>

2. Input

import { Input } from '@fabrigeas/react-components';

# params:
# all react input params plus the following
# isValid?: booleam 
# {/* <Input value={} onChange={} /> */}
<Input isValid={true} />
<Input isValid={true} validFeedback='Looks fine' />
<Input isValid={true} invalid='This field cannot be left empty' />

3. Icon

import { Icon } from '@fabrigeas/react-components';

# params:
# all span params plus 
# icon: 'trash' | 'sort' | 'list' | 'home' | 'next'
<Icon icon='trash' />
<Icon icon='home'/>

4. IconButton

  <Button>
    <Icon icon="sort" />
    Sort
  </Button>

Contribution

git clone @fabrigeas/react-components
cd react-components
# make your changes and commit
# create a merge request and assign it to me '[email protected]'

Deployment

# A grunt task has been configured to automatically deploy this package

grunt publish:major # increment the npm major version, then publish to npm and push to git
grunt publish:minor # increment the npm minor version, then publish to npm and push to git
grunt publish:patch # increment the npm patch version, then publish to npm and push to git
grunt publish # equivalent to grunt publish:patch
grunt publish:typo # equivalent to grunt publish:patch