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

mingine

v1.0.2

Published

A Node.js module to understand your dependencies `engines`.

Downloads

4

Readme

mingine

A Node.js module to understand your dependencies engines.

Usage

First, you'll need to install mingine:

npm i migine

Next, you'll want to require and use migine. Requring mingine returns a promise that resolves an object.

const mingine = require('mingine')

async function getNodeMinimumEngine () {
  const engines = await mingine() // mingine returns a promise

  console.log(engines.node ? engines.node.minimum : undefined) // will log the minimum usable version of node.js if there were any `engines` that included `node`, otherwise it'll return undefined
}

getNodeMinimumEngine()

mingine(options)

  • options object (optional) - An object that acts as a courrier of options to Arborist. Currently, only path is actively used.
    • path string (optional) - where to search for node_modules. defaults to the current working directory.

Returns promise - a promise that resolves an object, which represents the strucutre of engines. See [Returned Object Structure][] for more context on the shape of this object.

Calling mingine() by itself will return a promise that resolves an object. It searches the current working directory's node_modules to do so. Calling mingine(options) where options is an object and has the property path, the value of path will be used as the directory to search for node_modules.

Returned Object Structure

The structure of mingine's API is consistent, but the properties will not be. Mingine collects the engine property from every package inside of node_modules and then dynamically builds an object that includes every property within engines it encountered. It makes no assurances that any given property will exist since there's no gaurantee that a property may exist within node_modules.

The general structure will be:

  • ${engineName} object - an object where the key is the name encountered inside of the engines property of a given package.json. Examples: node, npm

    • versions object - an object that will always be identified as versions that contains arrays that represent each ${version} of ${engineName}
      • ${version} array - an array where the key is either a valid semver version OR any other string - even if it's not a valid semver version - since people do weird things with engines. In the future this may be tweaked/audited. Examples: 1.4.2, 10.0.0, 8.2.0
        • ${package} string - strings that represent the package names of packages that included ${version} as the value for ${engineName} in their package.json. Examples: webpack, react, qs, request
    • minimum string - a string that includes the minimum usable version of ${engineName} given the context collected from the engines property of all package.json files within node_modules.

    An example of JSON output can be found at ./examples/everything-output.json