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

build-data

v0.4.0

Published

Get metadata for your build

Downloads

11

Readme

build-data Build status for build-data

Get metadata for your build

Why?

  • Useful for managing build processes.
  • Reliable and concurrent data collection.
  • Intelligent behavior in or out of a repository.

Install

npm install build-data --save

Usage

Get it into your program.

const buildData = require('build-data');

Get the current branch name and a version to be associated with your build.

buildData().then((data) => {
    console.log('data:', data);
    // {
    //     branch  : 'master',
    //     version : '1.0.0'
    // }
});

Get the data that was used for the most recent build.

buildData.latest().then((data) => {
    console.log('data:', data);
});

You can and should provide any data you know already.

buildData({ version : '3.2.1' }).then((data) => {
    console.log('data:', data);
});

API

buildData(option)

option

Type: object

Settings and known build metadata.

cwd

Type: string Default: process.cwd()

The parent directory of the build root.

branch

Type: string

Use the given branch name, instead of asking git.

version

Type: string

Use the given version, instead of asking build-version.

buildData.latest(option)

Same as buildData(), except the branch defaults to the most recently built branch and version defaults to the most recently built version of the branch.

Related

Contributing

See our contributing guidelines for more details.

  1. Fork it.
  2. Make a feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request.

License

MPL-2.0 © Seth Holladay

Go make something, dang it.