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

@retirable/component-library

v1.8.0

Published

This package represents Retirable's component library [npm package](https://www.npmjs.com/package/@retirable/component-library). Download instructions:

Downloads

187

Readme

@retirable/component-library

This package represents Retirable's component library npm package. Download instructions:

yarn add @retirable/component-library

Contributing:

If interested in contributing, please email [email protected].

File structure rules:

  • Components are consolidated into folders with similar components - for example all buttons live within the buttons folder.
  • The styles associated with a particular component are defined in the same file that the component is defined within.
  • If a style is used in all the components within a particular folder, but does not itself have its own component, that style is defined within a styles folder and the file is named base[CategoryOfComponent]Styles.

Versioning:

Our component library uses semantic versioning conventions. The following provides a summary of this pattern.

[MAJOR].[MINOR].[PATCH]

  • The major version should be updated when a change breaks services that currently use the library. As an example, if a required prop is added to an existing component, updating to the latest version of the package will cause the existing components to break.
  • Minor versions should be updated when additional functionality, albeit non-breaking, is introduced. As an example, if a new variant is added to a component, the minor version should be updated.
  • Patch versions should be updated when backwards-compatible bugs are fixed.

Additional resources:

  • https://semver.org/
  • https://docs.npmjs.com/about-semantic-versioning