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

@olist/ui-commons

v0.28.0

Published

olist design language system

Downloads

285

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

israelcaxisraelcaxgabriel.ferrazgabriel.ferrazwallisonsilvawallisonsilvaeugeniobarroseugeniobarrosfelipe.nagelfelipe.nageltiagodalvitiagodalvipauloregispauloregislucaslennonlucaslennonaraujovitoraraujovitorpdrowfzpdrowfzrcasachircasachijulio.melojulio.meloarthuzugaarthuzugacalacacalacasamuelramoxsamuelramoxgomesgustavogomesgustavobatistaleandrobatistaleandrokroskakroskaeliezermarqueseliezermarqueseverton-cruzeverton-cruzcharles-bezerra-olistcharles-bezerra-olistandrermandrermrodrigo.alcydesrodrigo.alcydesromuloctbaromuloctbafgsouzafgsouzawallisonhenriquewallisonhenriquewesley.diaswesley.diasallyssonsantosallyssonsantosviclenviclentotabrazolisttotabrazolistsirluissirluis

Keywords

olistuiunited

Readme

olist commons ui

UI-commons is a library of components used in applications developed by olist.

Installing / Getting started

  yarn add @olist/ui-commons

After that you'll be able to import it in your project and use the components and helpers.

  import { createForm } from '@olist/ui-commons/utils';

Developing

Built With

It was built on top of React 16.

Prerequisites

  • Node version >= 8.9.0 <12.0.0.
  • Npm version >= 5.5.1.
  • It's fairly recommended using yarn for packages management.

Setting up Dev

Ok, you're looking forward to contributing, so follow the instructions.

If you're here, you already have access to the repository, haven't you? So, just clone the project and install the dependencies.

git clone [email protected]:olist/olist-ui-commons.git
cd olist-ui-commons/
yarn
yarn dev

If everything's ok with your environment, all dependencies should've been installed, but if something went wrong feel free to create an issue reporting the problem.

This starts building, watching the changes and running the server.

Building

  yarn build

Release

We're automanting with release-it, but it's not working yet. For now, you should manually change the version in package.json.

Tests

  yarn test
  // or
  yarn test:watch

Lint

  yarn lint

Publishing

To publish, just run:

  make publish

It'll assure that tests were run and UI-Commons was built along with its component styleguide documentation, and was deployed in Github Pages.

Style guide

Take a look at docz documentation