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

ctc-component-library

v0.1.93

Published

## Requirements ``` node v18.19.1 or above ```

Readme

ctc-component-library

Requirements

node v18.19.1 or above

Install

npm install --save @ctc-component-library

Run local

- npm install
- npm run storybook

To publish

- Increase the version on package.json
- Push to main branch, the actions to publish and deploy will be run

Material Symbols demo

- Here you can preview all the icons
https://marella.me/material-symbols/demo/

- Usage
https://github.com/marella/material-symbols/tree/main/material-symbols#usage

Installing yalc on Your Machine

Using NPM:

npm i yalc -g

Using Yarn:

yarn global add yalc

Updating the Library with yalc

Once yalc is installed, navigate to the root of the library and execute:

ctc-component-library % yarn yalc:update

Then, in the root of the project where the library will be installed (e.g., Backoffice), execute:

ctc-backoffice-frontend % yalc add ctc-component-library

Using the Components

Now you can use the components, for example:

import { Button } from 'ctc-component-library';

const SomeForm: React.FC = () => (
  <Button type="primary" text="Send" />
);

This allows you to have the library installed locally, make changes or adjustments to any component in the library, and validate them immediately without having to go through the process of pull requests, merges, and deployment to NPM.

Updating the Library in a Project

After making a change to a component in the library, and if you need to see this change in the project consuming the library, you must build and update the package in the local yalc repository. Then, remove and add the library package again in the consuming project. To do this:

Navigate to the root of the library and execute:

ctc-component-library % yarn yalc:update

Navigate to the root of the project consuming the library (e.g., Backoffice) and to remove the library, execute:

ctc-backoffice-frontend % yalc remove ctc-component-library

Then, to add the library, execute:

ctc-backoffice-frontend % yalc add ctc-component-library