ES2015 boilerplate for creating libraries with the newest front-end technologies.

  • boily

Downloads in past


5.2.46 years ago7 years agoMinified + gzip package size for boily in KB


ES2015 boilerplate for creating libraries with the newest front-end technologies.

Build Status Coverage Status npm version npm npm downloads


  • Rewire enables options to mock modules for testing purposes.
  • Stub let you stub module exports at runtime when bundling with Rollup.
  • Chai as Promised extends Chai with a fluent language for asserting facts about promises.
  • Eslint to maintain a consistent code style
  • Flow for quickly find errors in JavaScript applications
  • Livereload an implementation of the LiveReload server in Node.js.
  • Unit tests written with ES2015 get transpiled on the fly
  • Browser tests in the browser
  • Node >= 5.x

Quick start

The only development dependency of this project is Node.js. So just make sure you have it installed. Then type few commands known to every Node developer... ```js $ git clone $ cd boily $ npm install # Install Node modules listed in ./package.json $ npm run build # Build a minified and a non-minified version of the library ``` ... and boom! You have it all setup for you!


  • npm run build - Build task that generates both minified and non-minified scripts
  • npm run build:prod - Build task that generate a minified script
  • npm run build:dev - Build task that generate a non-minified script
  • npm run build:es6 - Build task that generate and preserves ES6 imports and exports into a ES2015 development bundle
  • npm run build:closure - Build task that generate a Google Closure bundle
  • npm run build:common - Build task that generate a CommonJS bundle
  • npm run build:all - Runs all build tasks
  • npm run lint:source - Lint the source
  • npm run lint:tests - Lint the unit tests
  • npm run lint:gulp - Lint the gulp file
  • npm run lint:all - Lint everything. Source files, test and the gulp file
  • npm run clean - Remove the coverage report - and the dist folder
  • npm run server:cov - Run Isparta, a code coverage tool
  • npm run test - Runs unit tests for both server and the browser
  • npm run test:browser - Runs the unit tests for browser
  • npm run test:server - Runs the unit tests on the server
  • npm run karma:chrome - Runs the unit tests for browser with Chrome
  • npm run karma:phantom - Runs the unit tests for browser with PhantomJS
  • npm run karma:ie - Runs the unit tests for browser with Internet Explorer
  • npm run karma:firefox - Runs the unit tests for browser with Firefox
  • npm run watch:server - Run all unit tests for server & watch files for changes
  • npm run watch:browser - Run all unit tests for browser & watch files for changes
  • npm run watch:chrome - Run all unit tests for browser with Chrome & watch files for changes
  • npm run watch:firefox - Run all unit tests for browser with Firefox & watch files for changes
  • npm run watch:phantom - Run all unit tests for browser with PhantomJS & watch files for changes
  • npm run packages - List installed packages
  • npm run packages:purge - Remove all dependencies
  • npm run packages:reinstall - Reinstall all dependencies
  • npm run packages:check - shows a list over dependencies with a higher version number then the current one - if any
  • npm run packages:upgrade - Automatically upgrade all devDependencies & dependencies, and update package.json
  • npm run browser - runs browser unit tests in the browser. All of your unit tests get bundled automatically.

Testing environment

This project uses Mocha to run your unit tests, it uses Karma as the test runner, it enables the feature that you are able to render your tests to the browser (e.g: Firefox, Chrome etc.). To add a unit test, simply create a .spec.browser.js or a .spec.server.js file inside the ~../specs/ folder. Karma will pick up on these files automatically, and Mocha and Chai will be available within your unit tests without the need to import them. To run unit tests only for the browser ( client), or for the server, create either a ~/.spec.browser.js or ~/spec.server file inside the same folder. To run the tests in the project, just simply npm run test for both server and client unit tests, or npm run test:server. for server or npm run test:browser. for browser tests. To keep watching the common test suites that you are working on, simply do npm run watch:browser or npm run watch:server. Note! By default all server tests are run with JSDOM

Adding other test files

  • Browser:, simply open up the karma.conf.js file in the ~/config folder and add your files to the files: and preprocessors: section.
  • NodejS: open up the gulpfile.babel.js file and add your files to the top of the file.
Note! Karma runs both browser and nodejs unit tests by default.

Browser tests

The browser spec runner - ./config.runner.html - can be opened in a browser to run your tests. For it to work, you must first run npm run browser. This will set up a watch task that will automatically refresh the tests when your scripts, or the tests, change.


Only syntax parsing are supported. If you want to transform JSX you need to add a JSX transformer plugins for it. E.g babel-plugin-transform-react-jsx for React support.


Both parsing and transformation of Flow comments are supported by this boilerplate.


Rewire is supported through the babel-plugin-rewire plugin. It is useful for writing tests, specifically to mock the dependencies of the module under test. Examples and tests are included.


Sinon.JS is also set up for test doubles - see BatClass.common.js for examples of both Sinon and Rewire using ES6 classes.


This library is set up to integrate with Coveralls, and will automatically publish your coverage report to if you have created an account there.


Rollup are used as the library bundler. It bundle down to a cleaner and more lightweight bundle then what you get with for example Webpack and Browserify.

Package management

Boily has build-in some nice features to always make sure your dependency tree are up to date. To check for the latest dependencies, simply run npm run package:check. If you want to update your packages, you can simply do npm run package:upgrade. Note! Your package.json will be automatically updated so make sure you have saved your changes before running this. To reinstall all packages, do npm run package:reinstall, and to remove all packages npm run package:purge.


This boilerplate uses a pre-commit hook to ensure that your npm test (or other specified scripts) passes before you can commit your changes. This all conveniently configured in your package.json.


jsdom are used to set up React.js components' testing harness under Node.js, based on the amazing jsdom. Also a couple of bugs related to React is fixed.


ESLint are used to lint your source. To change the rules, edit the .eslintrc file in the root directory, respectively.


Download the package, and run this from the command line: ``` npm install ```

Known issues

  • PhantomJS has it's limitation, and doesn't support ES2015 100%. Workaround is too use alternative Karma launcher. E.g. Chrome or Firefox.
  • JSDOM have issues with various things that work by default in native DOM. E.g. event listeners get invoked when they shouldn't, and boolean attributes not after the DOM specs.


Why isn't rollup used as a preprocessor for Karma?

Simply because Rollup doesn't support rewire. And there is no benefit in using it over Webpack. It could have solved an issue with Webpack and Karma, but the Istanbul plugin for rollup sucks big time. It's not a issue with the plugin itself.

Why use Gulp?

Gulp is used to get the coverage report working cross-browser without issues.

Is this backward compatible with Boily 2.x

Yes. Everything works the same.

What formats are supported?

commonJS, ES6, UMD, and all other know formats.

Is Google Closure supported?

Yes. You can't compile it, but you can bundle your code to output a non-minified Google closure script.
The MIT License (MIT) Copyright (c) 2016 KFlash Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.