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

version-attribute

v2.0.1

Published

Node package to help traverse and retrieve version keys and their properties (ex: 1.0.1) in an object.

Downloads

123

Readme

Build Status Coverage Status semantic-release

Version Attribute

This module assists with identifying object attributes that correspond to versioning naming schemes {major}.{minor}.{patch} ex: 1.0.1. It will accept any number of additional sub-patches, minor-version, or major-versions as long as new branch depths are consistent and demarcated with a ".". Ex: You can traverse an object with properties like 3.1.1.1 for instance, not just 3.1.1.

Given an object with version number properties and an array corresponding to a path [{major},{minor},{patch}] you can:

  • Determine if the path exists in the object.
  • Get the adjacent version number of a key in the object. (ex: you provide 1.0.1 you get back 1.0.0 - provided both of those keys exist)
  • Test for the existence of properties at or below a version number (ex: do i have a property of member at 1.0.1.member in an object?).
  • Get the property at its first occurence at or below the passed version number. (ex: returns the value of the first occurence of the property member starting at version 1.0.1 traversing adjacent lower version numbers)

Example

  • Let's say you have an object that is organized into version naming schemes - such as 1.0.1, 3.1.1 (similar to API version naming conventions.) Each level of the version scheme is another level in the object. Example:
// The version 1.0.1 would be represented by:
{
  1:{
    0: {
      1: {
        // This property represents version 1.0.1
      }
    }
  }
}
  • You might use such an object to store configuration properties. Example:
// A property of a version property:
{
  1:{
    0: {
      1: {
        members: {'gold'}
      }
    }
  }
}
  • Because you might have a lot of versions that you need to keep track of and properties are constantly changing, you could use inheritence to track changing properties in the versions. You may find this shorthand convenient for infrequenly changing properties.
// For an object with version attributes like this:
var versionObject = {
  1: {
    1: {
       members: ['silver'], // Members is silver in 1.1
       1: {
         members: ['bronze']  // Members is bronze in 1.1.1
       }
    },
    2: {
      otherProperty: ['gold']  // Other Property is gold in 1.2
    }
  },
  2: {
    members: ['silver', 'bronze'] // Members is silver and bronze in 2
  }
}

Usage

  • You can use version attribute to better understand this object.
// Review the example above for a more thorough explanation of the object.
// For an object with version attributes like this:
var versionObject = {
  1: {
    1: {
       members: ['silver'], // Members: silver in 1.1
       1: {
         members: ['bronze']  // Members: bronze in 1.1.1
       }
    },
    2: {
      otherProperty: ['gold']  // Other Property: gold, Members: bronze hierarchically.
    }
  },
  2: {
    members: ['silver', 'bronze'], // Members: silver,bronze, Other Property: gold in 1.2 hierarchically.
    1: {
      yetOtherProperty: ['tin'] // yetOtherProperty: tin, members: silver,bronze, and otherProperty: is gold hierarchically.
    }
  }
}

const VersionAttribute = require('../lib/versionAttribute')();
const versionAttribute = new VersionAttribute(versionObject);
var testPath;

// We can understand more about what version properties are in the object
// in the first place.

// Use getVersion to see if we have a version at or below the
// version (1.1.1) we provide in this object.
testPath = versionAttribute.getVersion([1, 1, 1]);
// testPath is [1,1,1] because that version exists in the object.

// getVersion will even work if you pass in a version number
// not in the object.
testPath = versionAttribute.getVersion([1, 1, 2]);
// testPath is [1,1,1] because 1,1,2 doesn't exist but [1,1,1] is a lower
//  version hierarcally.

// When getVersion can not get an object at the passed path, it will go
// up a sibling or parent. Once it goes up that sibling or parent it
// descends down that branch as far as it can so that you get the next
// highest adjacent version.
testPath = versionAttribute.getVersion([3]);
// testPath is [2,1] because [3] doesn't exist so it goes up a parent
// to [2] and then down to the lowest child [2,1].

// You might just want the next lowest version from a version.
// For that we can use getPreviousClosestVersion.  This behaves
// in a similar way to getVersion but only returns version properties
// below the passed version property.

// Get a version path below the given path in the object.
testPath = versionAttribute.getPreviousClosestVersion([1,2]);
// testPath is [1,1,1] because it is the next adjacent version.

// Finally we can learn some information about the properties of the
// version properties like members and otherProperty in
// the example above.

// We can learn where the highest occurence of a give property exists
// given the object and a starting path. The versions we get back
// conform to the behavior of getVersion above and always return the
// first occurence of a property at or adjacently above the version we
// specify. Get the highest position of an attribute at the path or below
// in version, returns [1,1,1]
testPath = versionAttribute.getVersionHasTarget([2], 'members');
// testPath is [1,1,1] because not finding the members property in v
// version 2, we ascended a parent and then deeply descended and continued
// looking until we found members at version [1,1,1]

// We can also request that property directly.
// Get the attribute returns [bronze]
var testProperty = versionAttribute([2,1], 'otherProperty');
// testProperty is ['gold]. We looked for `otherProperty` in 2,1,
// not finding it we ascended  to the parent [2], where we also didn't find it.
// So we ascended a parent [1] where we descended as far as possible to [1,2]
// where we finally found a property `otherProperty` and returned `[gold]`;