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

@marianmeres/release

v1.1.2

Published

Little helper script to automate releasing a new version tag.

Downloads

16

Readme

@marianmeres/release

Just a little helper script to automate package version bump fitting my needs. Basically a wrapper of npm version, git add, git commit and git tag.

If specified, npm version is executed over multiple sub dirs.

The script will prompt you for confirmation, unless called with --yes arg.

The workflow

  1. do work
  2. commit
  3. call npx release [-v major|minor|patch|x.y.z] (default is patch)
  4. confirm version change
  5. git push && git push origin vX.Y.Z manually

Todo

  • Automate point 5. from the above as well (after prompt confirmation)

Install and execute

# install
npm i -D @marianmeres/release

# and execute as node script directly
node ./node_modules/@marianmeres/release/release.js

# or as npm executable, via npx
npx @marianmeres/release
# or, if already installed, just
npx release

# to execute as package.json script, add to your package.json:
# ...
#  "scripts": {
#   ...
    "release": "release" # add args as needed
#  }
# ...
# and then run
npm run release

Single dir mode

# Will +1 increase "patch" segment of current version (major.minor.patch).
# Current version is read from ./package.json
npx release

# Will set version and tag to "v1.2.3" regardless of current
npx release -v v1.2.3

Multiple dirs mode

With multiple dirs, always the {cwd}/package.json is read as the significant one to be bumped. All other dirs (specified via -d) are then synced accordingly.

.
├── .git
├── package.json
├── sub1
│   └── package.json
└── sub2
    └── package.json
npx release -d sub1 -d sub2