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

tyler

v2.0.8

Published

An interactive React.js CLI for building atomic components & utilities.

Downloads

48

Readme

tyler

An interactive React.js CLI for building atomic components & utilities.

| Conception | Installation | Usage | Contributing | | ---------------------------------- | -------------------------------------- | ------------------------ | -------------------------------------- |

🙋 Feature Requests

  • Step 1 Create an issue to inform the maintainers and other contributors about what you're working on.

  • Step 2 Fork the repository, develop and test your code changes and add any relevant documentation. Ensure that your commit messages describe the changes.

  • Step 3 Make a pull request.

Create an Issue

Scour the issues for an issue similar to what you'd be working on prior to starting a discussion. It's possible that someone else is already working on your idea, your approach is not quite right, or that the functionality exists already.

If not, click here to create a ticket for a feature request.

There is no style guide as of yet but attempt to keep your code as clean as possible and follow conventions already set out in the existing codebase.

Fork the Repository

Be sure to add the relevant tests before making the pull request, and ensure coverage hasn't suffered. Also update any documentation relvant to the changes you've made.

Make a Pull Request

Once you have made all your changes, tests, and updated the documentation, make a pull request against the main branch of the repository. Be sure to reference the original issue in the pull request - with either Refs #400 or Closes #400.

🚩 Issue Submission

Scour the issues for an issue similar to what you'd be working on prior to starting a discussion. It is possible that someone else has already raised something about the bug/issue you've found.

If not click here to create a ticket to describe the bug you've found.

There is no style guide as of yet but attempt to keep your code as clean as possible and follow conventions already set out in the existing codebase. We recommend using Hemingway when writing/editing documentation.

🎰 Change Log

See the CHANGELOG here.

📚 Contributors

| Zishan Ali | Robert White | | :-------------: | :-------------: | | Zishan Ali | Robert White |

📋 License

MIT License