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

mungwin-react-elements

v1.0.4

Published

A react component library for mungwin

Downloads

3

Readme

Mungwin React Elements

A React components library for Mungwin

Your Design counts

If you have a component you love and want to build, this is the place to build it before using it in any mungwin project.

Proposed workflow

  1. Checkout development branch
  2. Pull the latest changes from development with git pull
  3. Install the latest changes in development with npm install
  4. Create and checkout your new branch, name it as issue_name-issue_number/component_name or any other relevant name you choose
  5. Design your component
  • Your component should be reusable and customizable
  • You can use css file imports or @emotion/styled whichever you choose is up to you
  • Put your components in src/components/your_component_folder/YourComponent.component.js
  • If you choose to use styled components with @emotion/styled, put your styles in src/components/your_component_folder/YourComponent.styles.js and export them, then import them in YourComponent.js
  • If you choose to use css, put your styles in src/components/your_component_folder/YourComponent.styles.css , then import them in YourComponent.js
  1. Test your component with storybook
  • Put your component stories in src/components/your_component_folder/YourCompnent.stories.js
  • Test their functionality, it should look great
  1. Export your component for public consumption in src/index.js use the format export {default as YourComponent} from './components/your_component_folder/YourComponent'
  2. Lint your code
  • Run npm run lint:fix
  1. Commit your changes
  2. Push your code create a PR