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

ceed

v1.0.2

Published

CI/CD in js helpers

Downloads

545

Readme

ceed Build Status

Set of JS async utils making building pipelines in JS easier

Library is taking advantage of ES2017 async/await functionality to allow creating more readable scripts performing command operations.

Install

$ npm install --save ceed

Running

You need node 6+ with the --harmony flag or installed babel-cli

node --harmony app.js

or

./node_modules/.bin/babel-node app.js

Example app.js

const {
    run,
    commit,
    maybe
  } = require('ceed');

(async function () {
    await commit('mkdir -p build', {}, {verbose: true});

	const build = await maybe('bash ./script.sh -o build');

	if (build.failed) {
	  //handle fail
	  console.log('Failed with: ' + build.code);
	}

	const builtItems = await run('ls', {
	  cwd: 'build'
	}).catch(err => {
	  //handle run promise rejection
	});

	buildItems.values.forEach(file => {
		console.log(`${file} built successfully`);
	});

})();

API

Package exports three methods that share the same API with different way of handling errors.

  • ceed.run(command: string, [execOptions]: Object, [ceedOptions]: {verbose: false})
  • ceed.maybe(command: string, [execOptions]: Object, [ceedOptions]: {verbose: false})
  • ceed.commit(command: string, [execOptions]: Object, [ceedOptions]: {verbose: false})

See node.js child_process.exec options for all execOptions

ceedOptions:

  • verbose: boolean - output result of every command. Default false.

You can set verbose option globally by setting env variable CEED_VERBOSE to true.

ceed.run

Run is a basic method which wraps child_process.exec into Promise interface.

You can catch failed commands using Promise .catch(fn) syntax.

ceed.maybe

Maybe works like run, except when the command fails Promise is still resolved successfully. You can get script exit code and status checking .succeed, .failed or .code property in resolved object.

ceed.commit

Commit works like run, except on fail it throws an error instead of rejecting the promise and it outputs more failure details

Resolved/Rejected object structure

{
	code: number | string, //script return code
	error: Error, //.exec failure error object
	failed: boolean, //is .code different than 0
	succeed: boolean, //oposite of failed
	output: string, //value of stdout
	value: string, //trimmed .output
	values: Array<string>, //trimmed .output splitted by lines
	stderr: string // value of stderr
}

License

MIT © Maciej Dudzinski