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

get-package-info

v1.0.0

Published

Gets properties from package.json files in parent directories.

Downloads

887,678

Readme

get-package-info Build Status

Gets properties from package.json files in parent directories.

Installing

npm install get-package-info

Usage

getPackageInfo(props, dir, [cb])

Searches for properties from package.json starting from the given directory going upwards, until all properties are found. Properties are set to the first instance found, and not overwritten. It returns a promise that resolves with the results (see example below for the structure of the results object). You may also specify a node-style callback if you prefer.

props

An array of string properties to search for. Nested properties can be retreived with dot notation (ex: dependencies.lodash).

If an individual property is an array, it will search for those properties in order, and the first value found will be saved under all the given properties. This is useful if you want at least one of those properties, but don't want the search to fail when it finds one but not another. Ex: getPackageInfo([['dependencies.lodash', 'devDependencies.lodash']], dir) will search for lodash in both dependencies and devDependencies, and save whichever one it finds first under both properties in the results.

dir

The initial directory to search in. getPackageInfo(props, dir) will look for a package.json in dir, and get the requested properties. If all the properties are not found, it will look in package.json files in parent directories.

Example

var getPackageInfo = require('get-package-info');

getPackageInfo([['productName', 'name'], 'dependencies.lodash'], '/path/to/dir')
.then((result) => {
    console.log(result);
});

Possible output, depending on the directory structure and package.json contents:

{
    values: {
        name: 'package-name',
        'dependencies.lodash': '~3.0.0'
    },
    source: {
        productName: {
            src: '/path/to/dir/package.json',
            pkg: { ... }, // the parsed package.json this property came from
            prop: 'productName'
        },
        name: {
            src: '/path/to/dir/package.json',
            pkg: { ... }, // the parsed package.json this property came from
            prop: 'productName' // name uses productName's value because productName has priority
        },
        'dependencies.lodash': {
            src: '/path/to/package.json', // This property was found in a higher directory
            pkg: { ... },
            prop: 'dependencies.lodash'
        }
    }
}
*/

Handling Errors

If all the properties cannot be found in parent package.json files, then getPackageInfo() will reject it's promise (or callback with err argument) with an Error. err.missingProps will have an array of the properties that it could not find, and err.result will contain all the props that were found.

If any other error occurs(like I/O or runtime errors), getPackageInfo() will reject with that error itself.