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

@4th-motion/release

v1.0.3

Published

Bump a new version and update your changelogs with a single command.

Downloads

19

Readme

@4th-motion/release

Bump a new version and update your changelog with a single command.

Version License

Say goodbye to handwritten changelogs - with this tool, a GitHub release is created and all changes since the last version are automatically recorded in the changelog file. You can have a look at how such a generated changelog file looks like.

Terminal

Installation

Add this package as a devDependency to your project:

yarn add --dev @4th-motion/release

Usage

Once that is done, you can run the command:

yarn release

You will be asked which version you want to release. If you have entered a valid version, your changelog will be adjusted, a tag will be created and all changes will be pushed. When you use certain keywords for your commits (e.g. fix:, feat:, …) your commits will be sorted accordingly in the changelog.

Note: If you want to make sure your team adheres to specific commit rules, we recommend to use @4th-motion/git-hooks. There you can define your rules and make sure that only schematically correct commits are pushed.

Customize to your needs

This script takes the master branch as default. And the changelog file must be in the root folder of your project. If you want to change these settings, you can pass some flags to the script.

yarn release --branch release
yarn release --changelog docs/changelog.md

Further documents

License

Copyright © 2020 by 4th motion GmbH. Released under the MIT License.