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

@richardtan-redbite/ui-web-common

v1.12.1

Published

Itemit UI Library and Common Helpers

Downloads

75

Readme

itemit-web-common

Itemit UI Library and Common Helpers

This is a Next.js project bootstrapped with create-next-app.

Requirement

Node version - v16 and above. Make sure switching the node version to v16 (run nvm use within project)

Getting Started

First, install the dependency package:

npm install
# or
yarn 
# or
pnpm

then

npm run storybook
# or
yarn storybook
# or
pnpm storybook

You are ready to create components and test it in storybook!

Commit practise

  1. With using semantic-release, our whole package release can be fully automated with their help, we just need to standardise the process on making a commit (not PR):
fix: [xxxx] - consider as Patch / Fix release
feat: [xxxx] - consder as Minor / Feature release
perf: [xxxx] + BREAKING CHANGE: [xxx] on footer - consider as Major / Breaking Release
  1. Keep each commits small and easy to read if possible

Development

  1. Create a branch from master - eg: feature/setup-tailwind-css
  2. Make commits with following semantic-release standard.
  3. Make and push changes in the branch
  4. Once changes made and sufficient test is done, raise a PR in Github to beta.
  5. Once PR is approved, proceed merge to beta.
  6. New beta version will be release if follow commit practise, you can either inside PR / pipeline / repo's releases.
  7. Install new beta package into your changes project.
  8. QA tested completed, raise feature branch to master and follow the same step as 3 - 6.
  9. If more fix or changes is required, follow the same step as 3 - 6 but to beta.
  10. Remember to change your package version in your other repository branch before going to master.

Git Convention

Follow https://gist.github.com/qoomon/5dfcdf8eec66a051ecd85625518cfd13