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

@payly/react-components

v0.9.4

Published

[![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)

Downloads

138

Readme

react-components

JavaScript Style Guide

Instalação

npm i @payly/react-components

Uso

import React, { Component } from "react";

import { Modal } from "@payly/react-components";

class Example extends Component {
  render() {
    return <Modal />;
  }
}

Contribuição

É importante para o funcionamento da LIB que todos os novos componentes e features possuam teste unitário e de UI!

Regras para merge request e publicação:

  • Teste unitário
  • Code Review
  • Alterar a versão da lib
  • Changelog
  • Teste de ui no Storybook no diretório PRINCIPAL src/
  • Teste de ui no Storybook no diretório de EXEMPLO example/

O teste de UI dentro do exemplo é necessário pois os componentes testados são importados como uma Lib, com instalação via NPM, e não diretamente no diretório de componentes.

Novos componentes

No storybook, tanto no diretório PRINCIPAL quanto no diretório de EXEMPLO, é importante criar uma story para cada componente novo.

Para executar o Storybook, utilizar o seguinte bash:

  npm run storybook

Testes unitários

Para rodar os testes unitários execute

npm run test

Para receber o coverage dos testes unitários

npm run test:coverage

Libs de teste: