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

react-sirius-ui

v0.0.1

Published

Design system & UI library for React

Downloads

2

Readme

Sirius UI

Sirius UI is a design system / React UI library. It works with styled-components and styled-system. Published package at Github named @muhsis/sirius-ui.

Git

We only have _development and master as main branches. Every branch gets checked out from master branch and merged to _development branch after development completes. While creating branches please use the following convention to make it easier to understand branches' purposes.

epic      A big branch with loads of features in it
wip       Works in progress; stuff I know won't be finished soon
feat      Feature I'm adding or expanding
bug       Bug fix or experiment
junk      Throwaway branch created to experiment
chore     General tasks related to build/deployment system

Commit Messages

We categorise git commit messages based on the work being done. There are some tags you need to use before the actual commit message.

  • All commit messages should be lowercase.
  • You can use () parantheses after the tag. For example feat(documents) : ....

Here's the list for commit tags:

  • feat : Use it when developing a new feature.
  • fix : Use it when fixing a bug or broken functionality.
  • chore : Not strictly development related tasks. Maintainance etc.
  • refactor : Use when refactoring an existing code.
  • docs : Use when documenting stuff.
  • build : Use when doing a task related to build, continous integration, package publishing etc.
  • perf : Use when doing a task that will improve performance.
  • ci : Continous integration related stuff.
  • revert : Reverting some previous operation.
  • style : Only visual stuff.
  • test : Tasks relating to testing suite.

Here you can find some sample commit messages.

  • fix(addScope): only throw when defaultScope is defined
  • docs: changelog for 5.0.0-beta.10
  • chore(package): update @semantic-release/npm to version 4.0.0
  • feat: association hooks
  • feat(postgres): drop enum support
  • feat(validation): improve validation for type
  • refactor: indexes and uniqueKey
  • performance: remove terraformer-wkt-parser dependency