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

default-theme-mhd

v3.4.2

Published

**Please use yarn instead of npm**

Downloads

19

Readme

Installation

Please use yarn instead of npm

yarn install

Setup

  1. Create .env.development and .env.production files. Refer to .env.example file.
  2. Run yarn storybook to download tailwind preset from CMS.

Important Notes

To create a component

  1. Create a new branch in the following format component/component-name
  2. Add component interface in src/lib/models.ts file
  3. Create component in src/components folder.

To demo component in Storybook

  1. Create story in stories folder. Refer to official Storybook docs here.

Notes

  • [ ] Components props views interfaces should be shared in npm packages
  • [ ] Any component shouldn't have much logic and it can always assume it will take the props from the controller component
  • [x] Make a tailwind setup similar to the newsifier main project
  • [ ] Solidify interfaces and separate logic from view for these components
  • [ ] Create a @types (TS type definitions) and @helpers NPM package (create newsifier NPM account) for components
  • [ ] Setup storybook boilerplate
  • [x] Create README
  • [ ] Setup layout for pages
  • [ ] Sync styling for storybook and main project
  • [ ] Using next/images in storybook