Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/scotch/angular-brunch-seed
AngularJS + Brunch
https://github.com/scotch/angular-brunch-seed
Last synced: about 2 months ago
JSON representation
AngularJS + Brunch
- Host: GitHub
- URL: https://github.com/scotch/angular-brunch-seed
- Owner: scotch
- License: other
- Created: 2012-07-15T17:40:52.000Z (about 12 years ago)
- Default Branch: master
- Last Pushed: 2019-10-17T20:13:09.000Z (almost 5 years ago)
- Last Synced: 2024-06-19T07:03:09.267Z (3 months ago)
- Language: CSS
- Homepage:
- Size: 938 KB
- Stars: 228
- Watchers: 18
- Forks: 78
- Open Issues: 15
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
Awesome Lists containing this project
- awesome-seed - angular-brunch-seed - AngularJS + Brunch (Seed List / Angular)
README
# angular-brunch-seed
### A starter project for AngularJS using Brunch.io
[AngularJS](http://angularjs.org) + [Brunch](http://brunch.io)
#### ** MAJOR UPDATES **
v0.4.0 Bring with it some major changes. If you're upgrading from a previous release,
please run `./scripts/init.sh` and remove any bower components from `vendor`. Bower
now uses the `bower_components` directory.
Features:
* Coffeescript / Jade / Less / Stylus automatically compiled on save
* auto-reload during development saves you from manually refreshing the page
* Javascript / CSS minification for production
* [karma](https://github.com/karma-runner/karma) integration for
unit tests
* Bootstrap integration with themes.
* Source map support
## Alternate Versions
- [Livescript](https://github.com/clkao/angular-brunch-seed-livescript)
by [@clkao](https://github.com/clkao) - Uses [Livescript](http://livescript.net/)
instead of [Coffeescript](http://coffeescript.org/)
- [True North](https://github.com/scoarescoare/angular-brunch-true-north)
by [@scoarescoare](https://github.com/scoarescoare) - Uses [SASS](http://sass-lang.com/)
instead of [LESS](http://lesscss.org/)
- [brunch-on-asteroids](https://github.com/exlee/brunch-on-asteroids)
by [@exlee](https://github.com/exlee) - A minimalistic version that adds Generators,
Bootswatch themes, D3, and more.
- [angular-brunch-seed-modularized](https://github.com/sanfordredlich/angular-brunch-seed-modularized)
by [@sanfordredlich](https://github.com/sanfordredlich) - Demonstrates a modular
design, consistent with best practices and better suited for larger projects
## How to use angular-brunch-seed
* `git clone https://github.com/scotch/angular-brunch-seed.git` to clone
the **angular-brunch-seed** repository
* `cd angular-brunch-seed`
* `./scripts/init.sh` to install node packages
Or if you have **Brunch** installed run:
`brunch new https://github.com/scotch/angular-brunch-seed myapp`
You must also install packages using bower. Either
```
bower install
```
or
```
./node_modules/.bin/bower install
```
*NOTE:* Depending upon your connection and processor speed the build can take
a substantial amount of time (3 - 15 minutes). The bower step is particularly
slow, because it downloads the complete git history. If you think that there
might be a problems, check you network traffic. If the build is still
downloading then it's still working.
### Using Jade
You will find the jade files in the `app` and `app/partials` directories.
Upon save the Jade files will be recompiled to HTML and added to the
`$templateCache`. When reverencing a partial use the path should begin with
`partial/` and end with `.html`. For example the `app/partials/nav.jade` would
be referenced in the Angular javascript code as 'partials/nav.html'.
*NOTE:* Behind the scenes Angular-brunch-seed uses
[jade-angular-brunch](https://github.com/GulinSS/jade-angularjs-brunch)
to compile and serve partials.
[jade-angular-brunch](https://github.com/GulinSS/jade-angularjs-brunch)
works by creating an Angular module named`'partials'` that adds the HTML
string of the partials to the `$templateCache`. For this to work you must add
`partials` to yours apps required modules list and include the `partials.js`
file in your `index.html` file.
If you are interested in the compiled HTML view the contents
of the `_public/js/partials.js` file.
### Using html
By default angular-brunch-seed uses jade templates. If you would prefer to use
HTML run the command:
```
./scripts/compile-html.sh
```
Open "app/app.coffee" and remove the dependency on 'partials' on the module App.
All Jade file will be compiled to HTML and be placed in the `app/assets` directory.
Additionally, the `*.jade` files will be removed from the project. Any changes
that you make to the `app/assets/**/*.html` files will now appear in the browser.
### Running the app during development
* `./scripts/server.sh` to serve using **Brunch**
Then navigate your browser to [http://localhost:3333](http://localhost:3333)
*NOTE:* Occasionally the scripts will not load properly on the initial
load. If this occurs, refresh the page. Subsequent refresh will render
correctly. Also, the initial load will take longer then subsequent loads,
some where around 20 seconds is normal.
### Running the app in production
* `./scripts/production.sh` to minify javascript and css files.
Please be aware of the caveats regarding Angular JS and minification,
take a look at [Dependency Injection](http://docs.angularjs.org/guide/di)
for information.
### Using Bower
Angular-brunch-seed uses [Bower](http://twitter.github.com/bower/) for package
management. To add or update dependencies, modify the `component.json` file
and run `bower install`. The component will be added to the `vendor` directory.
### Running unit tests
* `./scripts/test.sh` to run unit tests with [karma](https://github.com/karma-runner/karma)
Notes:
- Karma will run tests on save. To insure that changes are saved be sure
to have `./script/server.sh` or `./script/development.sh` running in the console.
- Set the browsers that you would like to target in the `/test/karma.conf.js` file
E.g. `browser = ["ChromeCanary", "Firefox"]`
### End to end testing
* run the app in development mode as described above using a separate terminal
* `./scripts/test-e2e.sh` to run e2e tests with
[karma](https://github.com/karma-runner/karma) using Angular's scenario runner
### Common issues
Initial load does not render correctly; scripts are not loading.
- Occasionally the scripts will not load properly on the initial load. If this
occurs, refresh the page. Subsequent refresh will render correctly.
`EMFILE` error
- EMFILE means there are too many open files. Brunch watches all your project
files and it's usually a pretty big number. You can fix this error with
setting max opened file count to bigger number with command `ulimit -n 10000`.
The complete [Brunch FAQ](https://github.com/brunch/brunch/blob/master/docs/faq.rst)
### Receiving updates from upstream
When we upgrade Angular-brunch-seed's repo with newer angular or testing library code,
you can just fetch the changes and merge them into your project with git.
```bash
git pull origin master
```
## Directory Layout
_public/ --> Contains generated file for servering the app
These files should not be edited directly
app/ --> all of the files to be used in production
assets --> a place for static assets. These files will be copied to
the public directory un-modified.
img/ --> image files
partials/ --> angular view partials (partial HTML templates)
nav.html If you are using HTML you may modify these files directly.
partial1.html If you are using Jade these file will be update from their *.jade counterpart
partial2.html
index.html --> app layout file (the main html template file of the app).
partials/ --> Jade partial files. This file will be converted to HTML upon save.
nav.jade If you are using HTML this directory will not be present. You will find the template file
partial1.jade in the `app/assets/partials` directory instead.
partial2.jade If you are using Jade these file will be converted to HTML and compiled into
`_public/js/partials.js` upon save.
scripts/ --> base directory for app scripts
controllers.js --> application controllers
directives.js --> custom angular directives
filters.js --> custom angular filters
services.js --> custom angular services
styles/ --> all custom styles. Acceptable files types inculde:
less, and stylus
_override.less --> styles that should be loaded after bootstrap.
_variables.less --> bootstrap variables to be used during the compilation process
--> **NOTE the underscore (_). Files begining with an underscore
will not automatically be compiled, they must be imported.
app.less --> a file for importing styles.
app.coffee --> application definition and routes.
index.jade --> Index file. This will be converted to assets/index.html on save
init.coffee --> application bootstrap
bower_components/ --> The bower_components dirctory is populated by Bower.
It contains Angular, Bootstrap Font-Awesome
and other utility files.
node_modules --> NodeJS modules
scripts/ --> handy shell scripts
compile-html.sh --> compiles *.jade file to *.html file and places them in app/assets
compile-tests.sh --> compiles coffeescript test to javascript
development.sh --> compiles files and watches for changes
init.sh --> installs node modules
production.sh --> compiles and compresses files for production use
server.sh --> runs a development server at `http://localhost:3333`
test.sh --> runs all unit tests
test-e2e.sh --> runs all end-to-end tests using Testacular
test/ --> test source files and libraries
app/
scenarios.coffee --> end-to-end specs
unit/
controllers.spec.js --> specs for controllers
directives.spec.js --> specs for directives
filters.spec.js --> specs for filters
services.spec.js --> specs for services
vendor/
test-results.xml --> Karma test resuls
karma-e2e.conf.js --> Karma end-to-end tests config
karma.conf.js --> Karma unit tests config
vendor/ --> The vendor directory is can be used for 3rd Party libraries.
Any files located in this directory will be included in js/vendor.js
bower.json --> Bower component config
config.coffee --> Brunch config
package.json --> node modules config
## Contributers
[Complete list of code contributers](https://github.com/scotch/angular-brunch-seed/graphs/contributors)
For more information on angular please check out