JSPM

minibase-control-flow

0.1.0
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 7
  • Score
    100M100P100Q31524F
  • License MIT

Plugin for [minibase][] and [base][] that adds control flow methods `.serial` and `.parallel` to your application, based on [each-promise][]

Package Exports

  • minibase-control-flow

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (minibase-control-flow) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

minibase-control-flow NPM version NPM downloads npm total downloads

Plugin for minibase and base that adds control flow methods .serial and .parallel to your application, based on each-promise

code climate standard code style linux build status windows build status coverage status dependency status

Table of Contents

(TOC generated by verb using markdown-toc)

Install

Install with npm

$ npm install minibase-control-flow --save

or install using yarn

$ yarn add minibase-control-flow

Usage

For more use-cases see the tests

const minibaseControlFlow = require('minibase-control-flow')

API

Contributing

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.
Please read the contributing guidelines for advice on opening issues, pull requests, and coding standards.

In short: If you want to contribute to that project, please follow these things

  1. Please DO NOT edit README.md, CHANGELOG.md and .verb.md files. See "Building docs" section.
  2. Ensure anything is okey by installing the dependencies and run the tests. See "Running tests" section.
  3. Always use npm run commit to commit changes instead of git commit, because it is interactive and user-friendly. It uses commitizen behind the scenes, which follows Conventional Changelog idealogy.
  4. Do NOT bump the version in package.json. For that we use npm run release, which is standard-version and follows Conventional Changelog idealogy.

Thanks a lot! :)

Building docs

Documentation and that readme is generated using verb-generate-readme, which is a verb generator, so you need to install both of them and then run verb command like that

$ npm install verbose/verb#dev verb-generate-readme --global && verb

Please don't edit the README directly. Any changes to the readme must be made in .verb.md.

Running tests

Clone repository and run the following in that cloned directory

$ npm install && npm test

Author

Charlike Mike Reagent

License

Copyright © 2016, Charlike Mike Reagent. Released under the MIT license.

This file was generated by verb-generate-readme, v0.2.0, on November 19, 2016.