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

@manomano/toolkit

v3.0.8

Published

mano-toolkit component library

Readme

  • Copyright (c) Colibri SAS - ManoMano
  • This source code is licensed under the MIT license found in the LICENSE file in the root directory of this source tree.

Manoolkit

Demo of currently available components: Demo Toolkit (activate your VPN)

version 0.1.0

Minimum Requirements

| React | React-DOM | Node | | ----- | --------- | ---- | | 16.4 | 16.4 | 8.9 |

Installation

yarn add @manomano/toolkit

or

npm install @manomano/toolkit --save

Usage

import { component } from '@manomano/toolkit';

Warning

Some components have external dependencies that increase the final bundle size.

  • React-table(41.29KB)

    • Table
  • React-Spring(31.79KB)

    • Alert
    • HeightTransition
    • Modal
    • OptionContainer
    • Overlay
    • Stepper
    • Tabs
    • TabBody
    • ToggleDown
    • Tooltip

Releasing new version of the Toolkit

In order to release a new version of the Toolkit, the Publish job of the master pipeline of GitlabCI needs to be triggered.

Then Semantic Release will analyse the name of every commits in the repository. This is why we recommend to squash every commits from the same branch and open a MR with a name following angular-commit convention (as mentioned below)

Gitlab MR name

prefix(scope): Name of the commit

Gitlab Description content

Description that might contain BREAKING CHANGE: here is the content of the breaking change

prefix

| prefix by | effect on v1.2.3 | | ------ | ------ | | chore | no version: v1.2.3 | | fix | patch version: v1.2.4 | | feat | minor version: v1.3.0 | | feat/fix with BREAKING CHANGE in Gitlab description | major version: v2.0.0 |

scope

Scope can be:

  • the name of one modified Component

Or some names of concerned work

  • dept for dependencies
  • test for general updates on tests

BREAKING CHANGE

Warning: As breaking changes are not related to any issues (no Jira issue will ask a developer to do breaking changes), the Semantic Release system is looking for BREAKING CHANGE words inside the description of Gitlab MR.

Some questions about Releasing Toolkit?

Feel free to ask ft-core-react some help