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

buck-trap

v1.0.15

Published

Buck Trap helps you to BUmp Changelog Kiss Tag Release and Publish your repo

Downloads

5

Readme

buck-trap

Buck Trap helps you to BUmp Changelog Kiss Tag Release And Publish your repo

Buck Trap

Usage

npm install --save-dev buck-trap

Now add the following to your package.json scripts section

"buck-trap": "buck-trap -a"

So e.g.:

"scripts": {
	"test": "tape tests/*",
	"buck-trap": "buck-trap -a"
},
"dependencies": { 
    "buck-trap": "1.0.14"
}

Or if you don't like the defaults (deploy/auth.json for the token file and dist folder for the build folder)

"buck-trap": "buck-trap -a -t /absoulute/path/to/auth.json-file -af /absoulute/path/to/dist/folder"

Also add the name of your project to the repository section: "name": "organisation/repo-name"

So for example: "repository": { "type": "git", "url": "git+https://github.com/nens/buck-trap.git", "name": "nens/buck-trap" },

The auth.json file should like similar to this:

{
    "token": "Your-token-that-you-created-on-github"
}

You can create your tokens here: https://github.com/settings/tokens Grant the token full access under the repo section

If everything is setup run:

npm run buck-trap

Releasing hotfixes or patches

If a stable release is coming out release it and start a new branch for the stable release e.g.:

git checkout -b release4.0 

If stuff is fixed on this branch, the fixes can be rolled out as patches without affecting the mainline release track. To run buck-trap from this branch and to release the branch with its CHANGELOG.md

npm run buck-trap -- -b release4.0

The fixes and the CHANGELOG.md would have to be merged with master, which might give some merge conflicts. C'est la vie.