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

@reusejs/react-alerts

v0.0.1

Published

A library of reactjs alerts

Downloads

24

Readme

View Storybook Join Discord NPM version NPM downloads MIT License Storybook NPM Publish

React Navigations

View Storybook at: https://master--618170a92697cd003a33e813.chromatic.com

Where to write components?

  1. There is a src folder where you can write your components
  2. Whichever components you want to be exposed would go into: index.js

Workflow

There are two ways you can develop components.

Storybook

  • Run: yarn storybook which will run the storybook in your localhost
  • When you write your own component, also write a .stories.jsx and storybook would pick it up

Another ReactJS App

  • Create a brand new react js app (Ex: my-app) using following: https://reactjs.org/docs/create-a-new-react-app.html#create-react-app
  • Run yarn link in current component library. Ex: If you component name is react-alerts, you would run yarn link inside react-alerts
  • Go to newly created reactjs app (my-app) and run yarn link @reusejs/react-alerts
  • At the same time also run yarn serve in react-alerts, so that as you make changes, build happens simultaneously and your my-app refreshes it

Contributing

New components

Hit us on discord on ideas channel. Propose your ideas, we will blow our brains out.

To existing components

Right now we don't a lot of hard and fast rules.

Just follow: https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow

Basically:

  • Fork the component to which you want to contribute
  • Make your changes, test it properly
  • Raise a Pull Request

Releases

Once your pull request is made, a release would be schedule which will push the library to npm to @reusejs org. You can't push to reusejs org.

License

react-alerts is freely distributable under the terms of the MIT license.