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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@they-consulting/react

v1.1.0

Published

Helper modules for an easier react life

Readme

They React

Collection of modules for an easier React life

Table of Contents

Use in your own project

See the Storybook for a list of available UI components.

Prerequisites

Usage

Install the package:

npm install @they-consulting/react
yarn add @they-consulting/react

Then you can use the components in your project:

import { CopyToClipboardIconButton } from '@they-consulting/react';

const MyComponent = () => {
  return <CopyToClipboardIconButton value="Hello World!" />;
};

Modules

Clipboard

useCopyToClipboard

A hook that copies a given value to the clipboard.

import { useCopyToClipboard } from '@they-consulting/react';

const MyComponent = () => {
  const { copied, handleCopy } = useCopyToClipboard('Hello World!');

  return <button onClick={handleCopy}>{copied ? 'Copied' : 'Copy to clipboard'}</button>;
};

CopyToClipboardIconButton

A button that copies a given value to the clipboard.

import { CopyToClipboardIconButton } from '@they-consulting/react';

const MyComponent = () => {
  return <CopyToClipboardIconButton value="Hello World!" />;
};

Contributing

Prerequisites

Local Dev

Install dependencies:

npm install

Start the Storybook server:

npm run dev

Adding new dependencies

If you add a new dependency, you need to decide if it should be bundled with the library or not. In case it should be bundled, add it to the dependencies in the package.json. Otherwise, include it in both devDependencies and peerDependencies instead. Also make sure to include peer dependencies that should not be bundled to the externals in vite.config.ts. For this to work, the import source must be identical to the external entry:

import { Box } from '@mui/material'; // this matches the external entry and will not be bundled

import { Box } from '@mui/material/Box'; // this doesn't match and will be bundled

Deployment

NPM

The package is automatically published to npm when a new release is created. Before creating a new release, make sure to update the version in the package.json. We use semantic versioning.

Docs

Storybook is automatically deployed to GitHub Pages when a new commit is pushed to the main branch. A GitHub action runs that builds and deploys the storybook to the gh-pages branch.