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

@internshipsamyrai44-ui-kit/components-lib

v0.0.2

Published

- clone the project: ```shell git clone [email protected]:internshipsamyrai44/components-lib.git ```

Downloads

212

Readme

Getting started

  • clone the project:
  git clone [email protected]:internshipsamyrai44/components-lib.git
  • switch to dev branch:
  git checkout dev
  • install project dependencies:
  pnpm install
  • the project is hosting and available on http://localhost:5173

Development

  • all development is focused in dev branch

  • to start your task you have to create a new branch from the dev branch. A name for this branch gotta reflect your current task. When the task is done you must commit to your current branch, then switch to dev and pull all changes from it. Resolve merge conflicts, if there are any. Then create a new pull request. ❗ Don't forget to check if you're actually pointing to the dev branch!

  • Follow this guide to write the commit messages in the right way! Briefly: add prefixes to the commit names, start them with a small letter and put the colon with the space (': ') after it at the end. For example:

    • feat: – new feature implemented (added footer, product card, some api request or component logic etc.)
    • fix: – fixed some error(s).
    • refactor: – removed, added or moved files, edited code formatting (white-space, formatting, missing semi-colons, etc), improved some algorithms etc.
      See more prefixes in the guide above.

React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

  • Configure the top-level parserOptions property like this:
export default {
  // other rules...
  parserOptions: {
    ecmaVersion: 'latest',
    sourceType: 'module',
    project: ['./tsconfig.json', './tsconfig.node.json', './tsconfig.app.json'],
    tsconfigRootDir: __dirname,
  },
}
  • Replace plugin:@typescript-eslint/recommended to plugin:@typescript-eslint/recommended-type-checked or plugin:@typescript-eslint/strict-type-checked
  • Optionally add plugin:@typescript-eslint/stylistic-type-checked
  • Install eslint-plugin-react and add plugin:react/recommended & plugin:react/jsx-runtime to the extends list