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

@proximahq-dev/components

v1.3.21

Published

- **Components Folder:** Always create a new folder for page specific components e.g. src/components/PageName - **Shared Components:** Any component used on more than one page should be added to src/components/shared - **Page Registry:** TBC, currently ea

Downloads

133

Readme

How to use

  • Components Folder: Always create a new folder for page specific components e.g. src/components/PageName
  • Shared Components: Any component used on more than one page should be added to src/components/shared
  • Page Registry: TBC, currently each page requires the projectSlug as the Prop.

How to develop

  • Create component
  • Add it to Storybook
  • Write unit tests
  • Execute "npx changeset" and choose appropriate version to bump
  • PR to main branch
  • Package will be deployed to NPM automatically

Versioning

Take the version 1.3.5 as an example.

  • "1" is the major change to the project - for incompatible API changes
  • "3" is the minor change - for backward-compatible functionality additions
  • "5" is the patch - for backward-compatible bug fixes

Bumping the major version resets both minor and patch versions to 0.

Bumping the minor version resets patch version to 0.

1.3.5 => 1.4.0

1.3.5 => 2.0.0