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

nitro-release

v0.1.1

Published

A release package for nitro. Manage your releases with ease.

Downloads

16

Readme

nitro-release

With this package, Nitro can produce releases by using gulp release on the CLI. You can influence the version bump by using the --bump option.

All possibilities in examples:

$ gulp release --bump
\> Version bumped from 0.0.0 -> 0.0.1

$ gulp release --bump=minor
\> Version bumped from 0.0.1 -> 0.1.0

$ gulp release --bump=major
\> Version bumped from 0.1.0 -> 1.0.0

$ gulp release --bump=patch
\> Version bumped from 1.0.0 -> 1.0.1

The release configuration can be found in config.json.

Configuration options

release.bumpFiles (Array)

A list of files, where a version bump should be processed.

  • example: ["package.json"]

release.commit (Boolean)

Defines, if the bumpFiles should be committed. A commit will have the message Release VERSION.

  • example: false

release.commitMessage (String)

Defines the commit message. Use %VERSION% to replace with current (bumped) version.

  • example: "Release %VERSION%"

release.push (Boolean)

Defines, if a commit should be pushed automatically. Only pushes, if commit is set to true.

  • example: false

release.pushBranch (String)

Defines the branch, which should be pushed. This should be the name of the branch, where the release happens.

  • example: "master"

release.pushTo (String)

Defines the remote origin name.

  • example: "origin"

release.tag (Boolean)

Defines, if a release git tag should be created. The name is vVERSION, e.g. v0.1.0.

  • example: false

release.tagName (String)

Defines the tag name. Use %VERSION% to replace with current (bumped) version.

  • example: "v%VERSION%"

Example Release Config

"release": {
    "bumpFiles": ["package.json"],
    "commit": false,
    "push": false,
    "pushBranch": "master",
    "pushTo": "origin",
    "tag": false
}