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

perfekt

v2.0.1

Published

Release and version your packages with perfe(k)t ease!

Downloads

20

Readme

Intro

perfekt is a release, changelog and versioning manager. It's easy to use and doesn't require any configuration to get it up and running.

Convention

For perfekt to run with its full power, your project must follow the conventional commits specification, this allows it to know the type of changes introduced in a given commit.

If your project doesn't do it yet, you can start any time as there is no need for rewriting any git history, simply create an initial release which will contain all of the unconventional commits and after that start naming your commits accordingly.

If for some reason you can't follow the convention for your commits' names, you can still use perfekt but you will lose some of the features, like grouping the commits by type or ability to automatically determine the next release version based on unreleased changes using new keyword in the perfekt release new command, about which you can read more here.

Getting started

For a quick introduction and set up instructions head to the getting started section.

You can also view the entire documentation online at lekterable.github.io/perfekt

Badge

Would you like to let the whole world know that your project is under the perfekt management?

management: perfekt👌

[![management: perfekt👌](https://img.shields.io/badge/management-perfekt👌-red.svg?style=flat-square)](https://github.com/lekterable/perfekt)

management: perfekt👌

[![management: perfekt👌](https://img.shields.io/badge/management-perfekt👌-red.svg?style=for-the-badge)](https://github.com/lekterable/perfekt)

License

MIT