Pkg
Stats

npm package discovery and stats viewer.

Discover Tips

General search
[free text search, go nuts!]
Package details
pkg:[package-name]
User packages
@[username]

Sponsor

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.

Twitter
@PkgStats
GitHub
pkgstats
Twitter
@ryanhefner
GitHub
ryanhefner
Site
ryanhefner.com

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 🙏

Framework
react / react-dom
Server
next / express / next-routes
Data Store
redux / react-redux / next-redux-wrapper / redux-thunk / redux-logger
Caching
lru-cache
CSS / Styling
next-page-transitions / styled-components
Typeface
@ibm/plex
Avatars
gravatar
Data Viz
chart.js / react-sparklines
Date formatting
dayjs
Infinite scrolling
react-scroll-trigger
Markdown rendering
react-markdown
Repository url parsing
hosted-git-info
User data
npm-user
Compiling
babel-plugin-module-resolver / babel-plugin-styled-components
Types
prop-types
Odds & Ends
es6-promise / isomorphic-fetch

© 2026 – Pkg Stats / Ryan Hefner

mungwin-react-widgets

v0.0.2

Published

4 years ago

# Your Design counts If you have a widget you love and want to build, this is the place to build it before using it in any mungwin project.

0High
0Medium
0Low

react widgets ui

Mungwin React Widgets

A React widgets library for Mungwin

Your Design counts

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

Proposed workflow

Checkout development branch
Pull the latest changes from development with git pull
Install the latest changes in development with npm install
Create and checkout your new branch, name it as issue_name-issue_number/component_name or any other relevant name you choose
Design you components

mungwin-react-elements is a dev dependency to this project, so the first place to start is there.
Break down your widget into small components, if you don't find a component in mungwin-react-elements, then you have to build it there first,
Link your projects and test first before creating you PR
- in mungwin-react-elements root folder, run npm link
- in mungwin-react-widgets root folder, run npm link mungwin-react-elements this will link both projects on your local machine, so you can develop components for your widgets in mungwin-react-elements and use them to develop mungwin-react-widgets before making you PR

Design your widget

You can use css file imports or @emotion/styled whichever you choose is up to you
Put your widgets in src/widgets/your_widget_folder/YourWidget.component.js
If you choose to use styled components with @emotion/styled, put your styles in src/widgets/your_widget_folder/YourWidget.styles.js and export them, then import them in YourComponent.js
If you choose to use css, put your styles in src/widgets/your_widget_folder/YourWidget.styles.css , then import them in YourWidget.component.js

Test your widget with storybook

Put your widtet stories in src/widgets/your_widget_folder/YourWidget.stories.js
Test their functionality, it should look great

Export your widget for public consumption in src/index.js use the format export {default as YourWidget} from './widgets/your_widget_folder/YourWidget.component'
Lint your code

Run npm run lint:fix

Commit your changes
Push your code create a PR