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

ci-build

v0.0.7

Published

Continuous integration build tool for node apps.

Downloads

8

Readme

ci-build

Continuous Integration build tool for node apps.

Usage

Command Line Interface

cibuild -cwd:/path/to/node/package -deploy

Configuration

###ci-build.json (per project)

{
    "rpmbuild": {
        "name": "dpscluster",
        "files": { "/var/local/dps-cluster/": "dist/**", "/etc/init/": "scripts/upstart/**", "/usr/bin": "bin/**" },
        "release": 1,
        "publish": {
            "channels": [ "dps-v6-64bit-dev-web" ]
        }
    },
    "deployment":{
        "include": [ "lib/**", "bin/**" ]
    }
}

rpmbuild - If omitted, RPM will not be built.

  • name - Name of RPM
  • files - json { "/my/install/path": "my/source/path/relative/to/cwd" }
  • release - Release number of RPM.
  • publish - If omitted, publish to spacewalk will be skipped.
    • channels - json ["my-spacewalk-channel"]

deployment

  • include - json [ "my/path1", "my/path2" ]

###config.json

headerText - Can include the following placeholders:

  • {{year}} - Current year.
  • {{gitHash}} - Current GIT hash.
  • {{buildVersion}} - Current version from package.json.
  • {{gitBranch}} - Current GIT branch.
  • {{buildNumber}} - Build number passed from Jenkins.
  • {{now}} - Current time.

CI Steps

  • Clean - Clean temp directories.
  • Version - Get GIT version information.
  • Test - Run mocha tests, linting, code coverage.
  • Build - Prepare dist directory.
  • Deploy - Publish to NPM, create RPM, push RPM to spacewalk.

Clean

  • Removes any temp directories left over by last build.

Version

  • Get GIT hash and branch information. Uses git cli.

Test

  • Mocha Tests - Make a call to shell npm test.
  • Linting - Perform linting using jshint. Uses .jshintrc file for global options.
  • Code Coverage - Perform code coverage using istanbul. This currently does not fail if code coverage is not met. Requires baseline_cover.js in test directory.

Build

  • Copy all deployment files to a dist directory.

Deploy

  • Publish package to NPM repo. Uses package.json publishConfig.
  • Package files into an RPM file.
  • Publish RPM to spacewalk using rhnpush cli.