This repo contains all core gulp dev tasks which can be configured and used in any FEAR projects alltogether or individually.

The tasks in this repo are provided in a factory function format for developer convenience, so you can use the functionality but can give any name to the task you create and configure it as much as the Core Task API makes it possible (see examples below).

Installation

To use any of the provided Core gulp tasks, please install the module first:

$ npm install --save-dev fear-core-dev

then to use:

require('fear-core-dev');

or use the fear-core installer module here

Further reading


Changelog

1.2.2

  • use mns-core eslint config npm module

1.2.0

  • use fear-core eslint config repo

1.1.13

  • replaced karma jspm dependendencies with system js

1.1.12

  • Install karma-mustache-preprocessor from github using SSH, as repo is now private

1.1.11

  • Install connect-mustache-middleware from github using SSH, as repo is now private

1.1.10

  • add stream-combiner2 for exit codes
  • update browser-sync version
  • update scss-lint version
  • update karma version
  • update karma-phantomjs-launcher version
  • Install connect-mustache-middleware from github using SSH, as repo is now private

1.1.9

  • dependency update

1.1.8

  • moved babel devDependencies to dependencies

1.1.7

  • added babel dependencies for karma

1.1.6

  • bumped karma-phantomjs-launcher to 1.0.0 dues to upgrading phantomjs version

1.1.5

  • decoupled module from other core modules
  • upgrade PhantomJS version to 2.1.3
  • removed data mock tasks

1.1.4

  • added sass lint install to module postinstall script

1.1.3

  • added documentation

1.1.2

  • first working npm publish


Contributing

Here's the most direct way to get your work merged into the project:

If your work is a new feature or a patch then follow the following workflow

  • Fork the project.
  • Clone down your fork ( git clone git@github.com:[username]/fear-core-dev.git ).
  • Create a topic branch to contain your change ( git checkout -b my_awesome_feature ).
  • Code away and add tests if applicable. Not necessarily in that order.
  • Make sure everything still passes by running npm run test.
  • Update the change log with details of the change and then mark in brackets what type of change it is (new feature/patch). The version of the next published version will then be decided by this.
  • If necessary, rebase your commits into logical chunks, without errors.
  • Push the branch up ( git push origin my_awesome_feature ).
  • Create a pull request against fear-core-ui/master and describe what your change does and the why you think it should be merged.

If your work is a breaking change please come to talk to the core team before commencing development.