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

@lavender-ai/lav-components

v1.4.26

Published

React components for use in Lavender Dashboard and Extension

Downloads

142

Readme

Lavender-Component-Library

React components for use in Lavender Dashboard and Extension

Install Instructions

npm i;
npm run storybook;

Publish a Version of this Library for internal use

  1. Update the package.json with a new version number. Please follow common numbering practices, follows the format MAJOR.MINOR.PATCH, where:
-  MAJOR version should be incremented for incompatible changes.
-  MINOR version should be incremented for backwards-compatible functionality additions.
-  PATCH version should be incremented for backwards-compatible bug fixes.
  1. In the terminal run the command
npm publish

This will publish the repo to the teams npm Organization under @lavender-ai

Errors in publishing

If you can not publish make sure you have the following.

  1. Do you have a NPM_TOKEN? This is created with your https://www.npmjs.com/settings/<your_account_name>/tokensaccount

  2. In your shell profile do you have your NPM_TOKEN set? In your .zshrc or .bashrc shell profile make sure you have the flowing

export NPM_TOKEN="<Your token>"

if you change this make sure you run source to for your terminal picks up the value.

source ~/.zshrc

or just close and open a new terminal window.

The top level .npmrc file in this repo will pickup that token to publish.

  1. Are you login to npm in the terminal?

To check if you are login to npm in your terminal run

npm whoami

If this errors out then you need to login via

npm login
  1. Are you invited to the npm Organization? Check with the Casey to see if you are invited

Adding a Custom Icon

Instructions listed in src/particles/Icon/README.md