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

cliengo-ui

v1.5.1

Published

Cliengo UI contains the React Components Library developed by the Cliengo Frontend team. <br> <br> Two projects live together within the repo: <b>Storybook Components Library</b> & <b>NPM Components Library</b>. <br> <br>

Readme

Cliengo UI

About the project

Cliengo UI contains the React Components Library developed by the Cliengo Frontend team. Two projects live together within the repo: Storybook Components Library & NPM Components Library.

Storybook Components Library

NPM Components Library

About

This project was bootstrapped with Create React App.

shields shields

Cliengo UI library contains react components written and used by the Cliengo front-end team.

Keep it general

Whenever you create a new component, keep in mind it could be used within any app, so it should be as general as possible. So, among other things:

  • Don't hardcode fonts
  • Don't hardcode images
  • Don't hardcode texts.

Production Usage

Installation

Run npm i -s cliengo-ui and then import the components you'd like to use. For example:

import {WhatsAppPreview} from 'cliengo-ui';

Release Phase

After testing in stage, and reviewing the corresponding Pull Request the following should be done. Before merging to master, a new release should be published using npm run release command. When prompted Select increment (next version): choose release and follow accepting al questions After the release is published. Merge should be done.

Stage Usage

Release Phase

For using the library in Stage or Review Apps, a prerelease version must be published. This is the workflow:

On your local branch run npm run release and follow the instructions. When prompted Select increment (next version): select: prerelease and follow accepting all questions

Notes:

  • All changes must be committed before running this command
  • Change the package.json version of cliengo-ui in the repo you are using the library (without using npm install, so it runs only the in RA)

version will be as follows: X.X.X-0 (the first time) , X.X.X-1 the second time and so on. To understand semantic versioning, please read: Semantic Versioning

Development usage

Storybook

After installing dependencies with yarn, you can run:

yarn storybook

Runs the app in the development mode. Open http://localhost:9009 to view it in the browser.

Deploying

Please review the Release Phase information for each environment (Development, Stage, Production) These commands are based on semantic versioning. If unsure about which command to use, please read semantic versioning documentation.

Deploy on github-pages

npm run deploy-storybook

Troubleshooting

If you're linking this package locally with another React app, and you're getting the following error:

Invalid hook call. Hooks can only be called inside of the body of a function component

It means the app is confused about which React library it should use. To address this issue, simply link the app's react library to this package, i.e. assuming you're in cliengo-ui folder:

npm link ../crm/node_modules/react

Note: Make sure to be using the correct version npm for running crm (at the date of writing, it's v8.15)

Source: https://github.com/facebook/react/issues/15315#issuecomment-479802153