Manages you Ender build.
This plugin requires Grunt
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-ender --save-dev
This is a temporary utility for handling Ender builds without having to always type
--output. Note that there is an official solution for this problem discussed on github that should be available soon. In the meantime, you can use this grunt task to help make using Ender easier.
Usage is simple. In your Gruntfile, add an
ender task and under the
options part you can specify the output location and the list of dependencies.
ender:options:output: "public/scripts/vendor/ender"dependencies: "bean" "bonzo" "qwery"
The example above would save the Ender build to "public/scripts/vendor/ender.js".
After this, you can run
grunt ender to build (or rebuild) your library. Use
grunt ender --info to see which libraries are currently in use.
dependencieskey of the package.json file as well. This way the grunt task doesn't have to deal with installing anything (assuming you run
npm installas usual) and you can specify the versions you need there.
grunt ender:buildit will actually rebuild the library from scratch. The regular Ender
removecommands are not utilized directly. This means that to add and remove libraries from the Ender build, edit your Gruntfile as appropriate.
In your Gruntfile.js
grunt ender or
grunt ender --info or
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.