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

federung

v1.0.4

Published

Helps with bumps

Downloads

20

Readme

Federung

Federung is an interactive CLI tool that helps you to change all your versions in one place. Federung is also the german word for suspension – because it helps with your bumps!

We use it for some build scripts where we may have to change some version numbers in some cases, but not every time. It can also help to just remind you to check if you incremented all the right numbers.

(We use it in combination with Expo to remind us to first update our build versions before starting new iOS and Android builds. But you can use it for whatever you want!)

Installation and Usage

First, install as a dev dependency:

npm install --save-dev federung

Federung uses Cosmiconfig. Add the federung key to your package.json and list the files and paths you want to get asked about when you run the tool:

{
  // ...
  "scripts": {
    // ...
    "deploy": "federung && deploy-update"
  },
  "federung": {
    "versions": [
        {
        "file": "app.json",
        "keyPath": "deploy.targetVersion"
      }, {
        "file": "app.json",
        "keyPath": "buildNumber"
      }
    ]
  }
}

In this example, the final output would look like this:

Federung lets you enter a new version for every keyPath. If you don't want to set a version, press enter to skip it. Federung will also do its best to keep the types of your version numbers the same.

In the example, we also added federung to the npm run deploy command. That way, whenever you run your deploy script, Federung will first ask you if you want to update any options.

Configuration

The configuration object takes one property, versions, which takes an array of places that Federung will look for version numbers:

{
  "versions": [
    {
      //  The file you want to open. Currently, only JSON files are supported.
      "file": "app.json" // string.

      // Path to your property. If the property is deep in your JSON, use a "." to drill down.
      "keyPath": "keyPath.to.your.property" // string.
    }]
}

Hint: We use lodash.get to interpret the keyPath, so anything that works with lodash.get will work.