Prebuilt Gulp environment for ES6+ web app boilerplates.
It comes with an ES6+ (ES7 async/await are there) to ES3-ish (as IE8 compatible as possible, but you may have to import polyfills, shims and shams accordingly) compilation process, together with a Browserify bundling and Uglifyjs compression.
Plus a CSS compilation task, to choose from one of the following:
as well as an Autoprefixer, post compilation, process (bye bye vendor prefixes).
Also, templates precompilation process, to choose from one of the following:
the task compiles templates in JST format, namespaces them under an
globally accessible variable and serves it to you in the form of a
module inside your static scripts folder.
You can also rely on a Karma tests runner, with PhantomJS and Google Chrome engines (bring your own karma.config.js file, though), plus JSHint code check and JSValidate safety checks on critical tasks.
It also gives you the possibility to serve your own instance of a Node.js server, plus watchers and livereloading for, well, everything really.
Bonus: version bumping and git tagging/pushing tasks.
gulpfile-sample.js in your app folder and configure it the way you
like. The configuration is pretty straightforward and the comments will help you
out on every bits of it.
You can also take a look at the gladius-draft's
gulpfile.js to see how
you can extend default tasks, add your own tasks or watchers, etc.
By default, the boilerplate will come with the following tasks, which you can extend or override as you please:
production: it will run the basic compilation + compression tasks, without tests
other than the JSValidate one to make sure everything worked fine.
development: it will run compilation tasks (no compression) with sourcemaps
support, plus it will run watchers to recompile and livereload everything as soon
as you make some changes, plus Karma in watch mode.
test: it will just run the tests without watchers (useful for CI engines).
patch are special tasks that handle the bump of the
version on the package.json as well as the bower.json if present, plus the tagging
on your git repo, and the push to master of the newly generated tag.
The boilerplate comes with a very basic set of dependencies installed via NPM. The remaining modules needed by each task will be lazily installed during the pre-process phase of each default task.
This way makes it possible to have the smallest amount of dependencies needed to
be installed for the
production task, that reflects on an massive reduction of
the installation footprint on production environment.
This boilerplate of mine is just a combination of great tools put together to achieve higher goals (using cutting edge technologies today, greatly simplifying a developer's workflow, etc), and if it weren't for the people who built those tools, I wouldn't have made this little thing so far.
So, thanks goes to: