Speed up your AngularJS development with a complete and scalable gulpjs based build system that scaffolds the project for you. Just focus on your app, angular-kickstart will take care of the rest.
What and Why
Install node.js. Then gulp and bower if you haven't yet.
$ npm -g install gulp bower
After that, install angular-kickstart downloading the master release (or clone the master branch if you want to run the development version).
$ git clone https://github.com/backand/angular-kickstart.git $ cd angular-kickstart
Install bower and npm dependencies, and run the application in development mode.
$ npm install $ bower install $ gulp serve
You are now ready to go, your application is available at http://127.0.0.1:3000.
Every file you add, edit or delete into the
/client folder will be handled by the build system.
When you are ready to build a production release there is a task for that:
$ gulp serve:dist
This task will lint your code, optimize css js and images files, run unit tests. After the task has successfully finished, you can find an optimized version of your project inside the
- Backand SDK included, just sign in to your app and the entire back-end is ready.
- 5 simple task:
- SASS continuous compiling.
e2etesting support. (for
- Livereload provided by browsersync.
- angular module dependencies automatically injected using ng-annotate.
- Static resources minification and optimization for production.
build/- Build files and configuration, the most important files to note are
karma.config.js. These files are the heart of the build system. Take a look.
client/the source code and tests of your application, take a look at the modules in this folder, you should structure your application following those conventions, but you can choose another convention as well.
.bowerrc- the bower configuration file. This tells Bower to install components in the
.jshintrc- JSHint configuration.
gulpfile- see The Build System below.
bower.json- Contains the list of bower dependencies.
package.json- node.js dependencies.
There are some
tasks available in
gulpfile.js. You can dig into the file to familiarize yourself with gulpjs.
A description of every available task:
- gulp serve - When this task runs, the build will take care of watching files. Every time you change a file in the
- gulp serve:dist - This task will run jshint and unit tests under the
client/test/unitfolder (thanks to
karma runner), and create a fully-optimized version of your application under the
build/dist/folder. The optimization consists of concatenate, minify and compress js and css files, optimize images, and put every template into a js file loaded by the application. A code coverage report will be available inside the
- gulp serve:tdd - Just like
gulp servebut in continuous unit testing environment.
- gulp test:unit - For running unit tests one time then exit.
- gulp test:e2e - Run end-to-end tests inside the
protractor. If a test fails, you should find a screenshot of the page inside the
client/test/screenshotsfolder. Note that you need to have the application running in order to run e2e tests. You can launch this task from another terminal instance.
PR and issues reporting are always welcome :)
See LICENSE file
See CHANGELOG.md file
Thank you, community!
All this wouldn't have been possible without these great contributors and everybody who comes with new ideas and suggestions.