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 🙏

© 2026 – Pkg Stats / Ryan Hefner

mdo-react-components

v2.0.62

Published

A mdo react components module boilerplat

Readme

MDO Components Node module boilerplate

A boilerplate for all the mdo react components

Instructions for sending repository

All operations is to publish mdo-react-components

  1. git checkout develop in local
  2. git pull (updated develop)
  3. git checkout -b
  4. git checkout master
  5. git pull (updated master)
  6. git checkout
  7. git rebase master (merged master to )
  8. if there is conflict, solve it
  9. increase one version patch(third number) number in package.json
  10. git push
  11. compare with develop in remote(github web page)
  12. After approval, merge to develop in remote
  13. create new pr to compare master with develop in remote. This step shouldn't have any conflict because we already solved it.
  14. After two approvals, merge develop to master.

Requirements

Quickstart

> yarn install

Build

After each change to this repository, please rebuild the boilerplate to make the changes effective using below command

> yarn build

Development

https://github.com/whitecolor/yalc

> yalc publish
> cd example && yalc add mdo-react-components

Unit tests

> yarn test

Component folder structure

Here is the default folder and files structure for each component:

  • components -- Example --- Example.js - this is component implementation --- styled.js - styles are here, we are using styled-components library --- index.js - import Example.js and maybe other components in this folder and then export them --- tests - folder with tests ---- Example.spec.js - tests for the component

Example component

When developing components follow the guideliens outlined here:

  • https://docs.google.com/document/d/1vs0f9hTi0FQxebNZmcGE6bM4SgQcSUvr4yff-kCnWjM/edit?usp=sharing
  • https://docs.google.com/document/d/1OeltaBvGRRV5f7z9Oe_rQt65NMqS3TYSfzAO3aDgIF4/edit?usp=sharing

Quick component example is below.

Example.jsx

import React, { memo } from "react";
import PropTypes from 'prop-types';

const Example = memo((props) => {
  const { prop1, prop2 } = props;
  return (
    <div>
      Something Here
    </div>
  )
});

Example.displayName = 'Example';

Example.propTypes = {
  prop1: PropTypes.number.isRequired, // try to limit the number of required props
  prop2: PropTypes.string
  ...
};

Example.defaultProps = {
  prop2: 'Default', // Default props only for not required props
}

index.js

import Example from 'Example';

export default Example;

Usage of the mdo-react-components library on other apps

In your application just import the components:

import { DataTable, CheckBox, /* other components */ } from "mdo-react-components";

Branching

Follow the guidelines outlined here: https://docs.google.com/document/d/1xZEeuOBfb6nFdhGzNyCuOPrT2CLTZiskRSKaIbD71ys/edit?usp=sharing

Pull Requests

As soon as you Each pull request must pass a review from another contributor and also pass the automated tests.

Useful links

License

This repository is protected under the MIT License

am-charts