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

@maany_shr/dad-ui-components-starter-template

v1.0.0-beta

Published

This template provides a extensive setup to create a component library of React Components.

Downloads

3

Readme

React Component Library Starter Kit

This template provides a extensive setup to create a component library of React Components.

This template comes with the following technologies configured and ready to go:

  • React
  • TailwindCSS
  • TypeScript
  • Vite
  • Vitest
  • Storybook
  • Automated CI testing, linting, formatting and coverage with GitHub Actions
  • Release automation with GitHub Actions and publishing to NPM
  • GitHub Pages Dashboard with API Docs, Storybooks and Test Coverage
  • Automatic Documentation Generation with TypeDoc
  • Winston for logging. There is a logging utility that can be used to log to the console

Getting Started

Begin via any of the following:

  • Press the "Use this template" button

  • Use degit to execute:

    degit github:dream-aim-deliver/dad-ui-components-starter-template
  • Use GitHub CLI to execute:

    gh repo create <name> --template="https://github.com/dream-aim-deliver/dad-ui-components-starter-template"
  • Simply git clone, delete the existing .git folder, and then:

    git init
    git add -A
    git commit -m "Initial commit"

Customizing the Template

Please go through the following checklist to ensure you have configured the template correctly:

  • [ ] Push your code to a new GitHub repository.
  • [ ] Update the test coverage thresholds in the vite.config.ts file.
  • [ ] Remember to use npm search <term> to avoid naming conflicts in the NPM Registry for your new package name.
  • [ ] Update the package.json file with your package name, version, description, author and repository information.
  • [ ] Add or update the LICENSE file.
  • [ ] In the GitHub repository, go to the "Settings" tab and select "Pages" section. Then select the source as "Github Actions".
  • [ ] Generate a new NPM Access Token.
  • [ ] Create a secret in the GitHub repository called NPM_TOKEN with the value of the npm access token from the previous step.
  • [ ] Update the README.md file by replacing <MY_COMPONENT_LIBRARY> with the name of your component library. Also, please update the href to point to your GitHub Pages URL.
  • [ ] Please read and update the Contributing Guidelines before contributing to this project.
  • [ ] Please go through the Release Guidelines before releasing a new version of this project.
  • [ ] Please make sure your developers have read the Development Guidelines before starting development.
  • [ ] Please remember to define the theme of your component library (colors, shades, fonts, animations, breakpoints etc..) in the tailwind.config.js file.
  • [ ] Once you have completed the above steps, you can delete the contents of this README.md file from here above. Please add any additional information about your component library at the end of this README. This file is used to generate the homepage for your NPM Package on npmjs.com and is also the homepage for your TypeDoc dashboard.

Your README.md Content goes here:

<MY_COMPONENT_REPOSITORY>