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

@wethegit/components

v3.0.0

Published

For how to use the components, see the [Documentation](https://wethegit.github.io/component-library/).

Downloads

259

Readme

@wethegit/components

For how to use the components, see the Documentation.

To learn how to contribute, continue reading.

Developing

It's important to know that this library is never compiled. The source files are provided as is. They are meant to be copied into your project.

Make sure you using the required Node version from nvmrc.

You will develop and test the components with Storybook.

From the root of the repository, run:

yarn
yarn start

This will start Storybook and watch for changes in the components' source files.

Adding components

When adding a new file, ensure the component is also exported from the main src/components/index.tsx file:

// src/components/index.tsx
export * from "./button"

Export only the necessary pieces of the component and their types from the component's index.tsx file.

// src/components/button/index.tsx
export { Button } from "./button"
export type { ButtonProps } from "./button"

Dependencies

If your component requires node packages as dependencies, add them to the peerDependencies and devDependencies:

Run these command from this directory, not from the root, otherwise they will be dependencies to the whole monorepo.

First add as a peer dependency:

yarn add <package-name> -P

Then as a dev dependency:

yarn add <package-name> -D

Node dependencies and types

If a component is using a node package without types, add a declaration file with the name of the package, without special characters, to the ./types directory:

// ./types/<package-name>.d.ts
declare module "<package-name>"

🧩 You are not done yet!

After you have added your component and is ready to release it, you need to add it to the CLI.

Add an entry to registry-index.ts following the required types described in that file.

After that's all done you can release a new version following the instructions in the project's readme.