@markchristopherbishop/pipeline
A pipeline allowing projects to be built, debugged, tested and shipped without the need for lengthy configuration or boilerplate code.
Last updated 4 years ago by markchristopherbishop .
ISC · Original npm · Tarball · package.json
$ cnpm install @markchristopherbishop/pipeline 
SYNC missed versions from official npm registry.

MCB Pipeline

A pipeline allowing projects to be built, debugged, tested and shipped without the need for lengthy configuration or boilerplate code.

MCB Pipeline exposes utilities to get projects up and running quickly. Install the pipeline then use its various commands in projects. The idea is to allow consumers to focus on their code rather than on the mechanics of building, debugging and testing that code.

Installation

In the target project run:

npm install @mcb/pipeline

Use

MCB Pipeline exposes a number of commands that you may use in npm scripts to facilitate your needs.

mcbp-build

This command will build a production ready version of the project into the dist directory. The command will uglify and optimise the bundle for distribution.

Please note, at present, it will expect to build the project from entry point ./src/index.js.

mcbp-debug

This command will build and host a live version of the application for debugging. The bundle will be built with sourcemaps for use in the browser. Source files will be hot loaded onto the server so that when you make changes, the bundle will be automatically rebuilt and the browser refreshed with your changes.

Please note, at present, like mcbp-build, it will expect to build the project from entry point ./src/index.js.

mcbp-unit-test

This command will execute a single unit test sweep of your code, perfrom a coverage scan and report all findings.

Tests will be sought in the following locations:

  • ./test (all .js files)
  • ./src (all files prefixed with .spec.js or -spec.js)

mcbp-unit-test-debug

This command will execute a live debugging session, for all located unit tests, to facilitate debugging.

Tests will be sought in the following locations:

  • ./test (all .js files)
  • ./src (all files prefixed with .spec.js or -spec.js)

Please note - this step requires Google Chrome.

Example use

The following shows the scripts section from a package.json file to demonstrate how a consumer might use MCB Pipeline:

"scripts": {
    "start": "mcbp-debug",
    "build": "mcbp-build",
    "unit": "mcbp-unit-test",
    "unit:debug": "mcbp-unit-test-debug"
}

Current Tags

  • 0.1.0                                ...           latest (4 years ago)

1 Versions

  • 0.1.0                                ...           4 years ago
Maintainers (1)
Downloads
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 0
Dependents (0)
None

Copyright 2014 - 2016 © taobao.org |