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

@vu.nguyen4nitecose/component

v0.1.6

Published

Base UI component for T1 project

Readme

Base design system for T1 project.

Required:

Node.js >= v16

yarn >= v1.22

Install dependencies

yarn install

Create new component

All of components are defined in src/core/components folder To start creating new component, needed to understand the type of component before creating new folder in the corresponding component type.

Example

Create new Input component

  • Go to the atoms folder, create Button folder contains those files:
├── Button
│   └── Button.tsx
│   └── Button.module.scss
│   └── index.ts
  • Button.tsx: Contains the React component of Button, contains HTML and logic inside component.
  • Button.module.scss: Contains Button's style
  • index.ts: To contains file export component

Then, in core/components/index.ts, declare the module component there to resolve the component.

export { default as Button } from './atoms/Button'

Visualize component using Storybook

  • Go to folder src/stories/ to see the structure corresponding with src/core/components/ folder
  • Create a file eg: Button.stories.tsx then write your story there.

All of the configurations of Storybook are in the .storybook folder

Storybook

To visualize components, run the Storybook by command:

yarn run storybook

or with npm

npm run storybook

Eslint

To see the error/warning about ESLint, run the command below

With yarn:

yarn lint

with npm:

npm run lint

To fix the warning ESLint, run the command below

With yarn:

yarn lint:fix

with npm:

npm run lint:fix

To format code using Prettier, run the command below

With yarn:

yarn format

with npm:

npm run format

Stylelint

To fix the warning/error about Stylelint, run the command below

With yarn:

yarn lint:style:fix

with npm:

npm run lint:style:fix

Commit conventional

All of the commits must be clearly and follow by Commitlint.

If you want to skip commit following Commit conventional, you can pass params --no-verify in the commit, but not recommended.

Build

  • For development or local mode:
yarn run build-dev
  • For development or local mode:
yarn run build-prod

The output directory is dist/ will be bundled on your root directory.

Change version

Based on the semantic versioning, you can change the version of the package by running the commands below

Major changed:

npm run bump-version-major

or with yarn:

yarn bump-version-major

Minor changed:

npm run bump-version-minor

or with yarn:

yarn bump-version-minor

Patch changed:

npm run bump-version-patch

or with yarn:

yarn bump-version-patch

Pack library

npm pack

You will see an extract file in your root project. Then you can install and use their applications

Or if you want to auto publish the package, you can run the following command:

npm run publish

or with yarn

yarn publish

Note: Must config version of package before publishing.

Copyright (c) 2023 by Niteco