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

@codux-pond/component-templates

v1.0.2

Published

<div align="center"> <img height="50" src="./src/assets/codux.svg"> <h1>Codux Component Templates</h1> </div>

Downloads

10

Readme

Component Templates

This project is a collection of component templates that can be used to create new components for the Codux. It is also contains a catalog of the components that are created using these templates as the main app.

How to create a new component template

Create a new folder in the src/component-templates directory with the component name in snake case all lowercase and dashed. (e.g. fancy-button, fine-card, tpl-input, etc.)

The folder should contain the following files: where COMPONENT_NAME is the name of the component. (same as the folder name)

  • COMPONENT_NAME.tsx - The component template.
  • COMPONENT_NAME.module.css - The component styles.
  • COMPONENT_NAME.component.json - The component packer metadata entry.
  • metadata - Directory containing the component metadata (will not be included in the installation).

Code Template Variables

The component template can contain variables that will be replaced with the actual values when the component is created. Currently, the following variables are supported:

  • ___COMPONENT_NAME___ - The name of the component.

Note:

We do not replace variables in all text files. We only replace variables in typescript, .css, .md and .json files. (this can be changed according to the requirement)

Casing Convention

There is a casing convention for the variables:

  • if the variable is title case, we replace it with the title case value.
  • if the variable starts with lower case, we replace it with the camel case value.
  • if the variable is in snake case, we replace it with the snake case value.

Components Catalog Scripts

In the project directory, you can run:

npm run build

Build the application in production mode into a folder named dist. This folder can be served using any HTTP server.

npm run dev

Start dev server, aliases: vite dev, vite serve.
Open http://127.0.0.1:5173/ to view it in the browser.

npm run preview

Boots up a local static web server that serves the files from dist at http://localhost:4173 . It's an easy way to check if the production build looks OK in your local environment.