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

pseudo-patch

v3.0.2

Published

fake patch on packageJson file

Downloads

33

Readme

pseudo-patch npm version

this was a silly edge case solve and an excuse to learn something new, published here so I can easily reuse, and hey.. it might be helpful to someone else out there ¯\_(ツ)_/¯

Install

yarn add pseudo-patch
{
  "scripts": {
    "pseudo-patch": "node ./node_modules/pseudo-patch"
  }
}

Usage

npm run pseudo-patch [opts]

What it does

nothing more then increase the package.json, by default and design it will be a patch update. But I later extended it out of bordem to support --major and --minor flags should anyone out there actuall want, or need it.

 {
  "name": "your-project",
-  "version": "1.0.0",
+  "version": "1.0.1",
 }

Options

$ pseudo-patch
    -s, --spacing <number>        Preferred JSON file indent spaces (defaults to 2)
    -p, --path <string>           path to package.json (if not <projectRoot>/package.json)
    --major                       force increment as a major change
    --minor                       force increment as a minor change