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

@thegrocery/toolkit

v2.9.1

Published

A design system developed and maintained by The Grocery

Downloads

5

Readme

Description

This is a toolkit repository for thegrocery organisation

CI/CD

We use act in order to test our workflows. Download the necessary binary, install it and run the below commands:

# If you want the agent to run on a different image
act -P ubuntu-22.04=ghcr.io/catthehacker/ubuntu:act-22.04 [push|pull_request]

# If you want to load secrets
act --secret-file=.secrets

# If you want to customize the github event [push|pull_request]
act -e=./event.json [push|pull_request]

# If you need to run a single job
act -j [jobName] [push|pull_request]

Storybook

What I have learned?

  • There are currently two ways to disable a control:
    • Use {[fieldname]: {table: {disable: true}}}
    • Use {parameters: {controls: {exclude: ['fieldName']}}}
    • If you want to disable controls globally, then you can achieve that using {parameters: {controls: {disable: true}}}
  • If you want to document a component, use a JSDoc comment before the declaration of the meta object
  • If you want to document a component property, pass the description property in the argTypes. e.g {argTypes: {[fieldName]: {description: 'something'}}}
  • If you want to document a story, add a JSDoc comment before the story declaration
  • If you want to configure storybook so it generates documentation for all components, then you need to update the main.ts file as below: {docs: {autodocs: true}}