ecc-gulp-tasks

Eccenca common gulp tasks (ecc-gulp-tasks)

A set of common gulp tasks for front-end development

Available tasks

• build - compiles optimized (minified, deduped) commonjs version of your component with webpack. Uses config.webpackConfig.production as basic configuration.
• build-app - compiles optimized (minified, deduped) application with webpack. Uses config.webpackConfig.application as basic configuration.
• debug - compiles debug version of your component with webpack, watches for changes and re-compiles when needed (until interrupted). Uses config.webpackConfig.debug as basic configuration.
• serve - uses express.js to statically serve folder specified in config.path at localhost:8080. Servers index.html for all non-existent requests to allow client-side routing testing. Allows access to express.js app via config.serverOverrides(app) function.
• test - runs mocha tests starting from file specified at config.testEntryPoint.
• bamboo-test - runs mocha tests starting from file specified at config.testEntryPoint and generates output with bamboo-mocha-reporter.
• cover - runs istanbul to generate test coverage from file specified at config.testEntryPoint.
• lint - runs eslint on files specified at config.lintingFiles.
• licenses-yaml2json - generates a licenses.json from a licenses.yaml file.

Usage

• Include into your project using npm i --save-dev ecc-gulp-tasks
• Create gulpfile.js looks like this:

var gulp = require('ecc-gulp-tasks')(require('./buildConfig.js'));

gulp.task('default', ['debug', 'serve']);

As you can see, you need to provide two arguments while requiring the package. First one is an array of string names of available tasks you wish to use. The second one is your build config (described below).

Adding custom gulp tassk

If you need to use your custom gulp tasks after including common ones, you can do it like so:

var gulp = require('ecc-gulp-tasks')(/* ... */);
// define task inline
gulp.task('my-task', function() {
    // ...
});
// load your custom tasks from external file
require('./gulp/my-other-task.js')(gulp);
// ...

How to run things synchonously?

Normally gulp runs everything asynchronously, but sometimes you might want to run tasks in sync. That is useful for example if you want to run tests and then build a component. To do that, you can use gulp-sequence package, like so:

var gulpSequence = require('gulp-sequence');
var gulp = require('ecc-gulp-tasks')(/* ... */);
// ....
gulp.task('deploy', gulpSequence('test', 'build-app'));

Build config

Example build config looks like this:

var path = require('path');
module.exports = {
    path: path.resolve(__dirname),
    testEntryPoint: path.join(__dirname, 'test', 'index.jsx'),
    webpackConfig: {
        debug: require('./webpack.config.js'),
        production: require('./webpack.config.prod.js'),
        application: require('./webpack.config.app.js'),
        common: {
            context: path.resolve(__dirname),
        },
    },
    licenseReport: {
        input: path.resolve(__dirname, 'license-report.yaml'),
        outputName: 'licenses.json',
        outputPath: path.resolve(__dirname, 'dist')
    },
    serverOverrides: function(app, express) {
        app.use(express.static(path.join(__dirname, 'dist')));
    },
    serverStart: function(server) {
        startSocketServer(server);
    },
};

Exported parameters are as follows:

• path - should point to directory you want to serve (used in serve task)
• testEntryPoint - should point to your test entry point (to be run by mocha)
• webpackConfig.debug - should include your webpack config used for debugging
• webpackConfig.production - should include your webpack config used for compilation for production
• webpackConfig.application - should include your webpack config used for compilation as production application. It allows for the following special parameters:
  • browsers: a browserslist definition which is used for css autoprefixing
  • copyFiles: a list of copy-webpack-plugin patterns which is used for copying files to the output folder
  • html: a html template for the html-webpack-plugin
• webpackConfig.common - may webpack config that webpackConfig.debug, webpackConfig.production and webpackConfig.application have in common
• licenseReport - should point to a license yaml file and contain parameters for the generated license report
• serverOverrides - should contain a function that can be used to override defaults from serve task
• serverStart - should contain function that can be used to start something on top of server instance (e.g. websocket server)

Javascript flags

There are the following flags set:

__WEBPACK__ is set to true while using gulp build|build-app|debug. This may be used for doing things only webpack can do, like requiring style sheets, etc:

if(__WEBPACK__){
  require('./style.css')
}

__DEBUG__ is set to true during gulp debug. If you run gulp build-app, __DEBUG__ is set to false, effectively stripping all debug statements. This may be used for doing things only during development:

// The following block will only be run during development
if(__DEBUG__){
  console.info('Dear Developer, have a nice day')
}

__VERSION__ is set to the result of git describe --always --dirty:

const version = (<div>{__VERSION__}</div>);