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

prme

v1.3.20

Published

Generate Pull Requests w/ plugin support

Downloads

21

Readme

pr

Pull Request Generator w/ Plugin support

npm version dependencies Build Status lifetimeDownloadCount

#Are you Lazy? So are we!

#Install

npm install -g prme

#Usage

prme

#Bam!

#Custom Configuration via pr-conf.json in your cwd

In your pr-conf.json

{
    "template" : "/myTemplateFile.mustache"

    "plugins": {
        "stackTrace" : {},
        "whatPlugins" : true
    }
}

This will output the native plugins installed,
 and the current result of the state machine

How it all works!

Native Plugins:

    [
        rally
        jenkins
        jenkinsBuildStatus
        github
        signOffs
        gitBranch
        gitUserRepo
        stackTrace
    ]

These are build right into pull-request-generator

You can build your own! 2 Ways

  1. require

    { "plugins" : { "require" : "myPublishedNPMPlugin" } }

  2. By Path

    { "plugins" : { "path" : "relative path to cwd of execution" } }

#How do I write a Plugin?

module.exports = function(allOpts, state, cb){

};

allOpts is your config file data

state is the current state of the state machine any modifications will affect later plugins and the mustache templating process

cb is your callback for when your done doing your changes