Use https://github.com/olov/ng-annotate in the Rails asset pipeline.
Add this line to your application's Gemfile:
gem 'ngannotate-rails'
And then execute:
$ bundle
That's it! ngannotate-rails integrates seamlessly into the Rails asset pipeline; your JavaScript or CoffeeScript assets will automatically be run through the ngannotate pre-minifier.
By default ng-annotate processing is disabled in development and test environments. Processing, however, can be enforced by specifying NG_FORCE=true option.
Options available as environment variables:
NG_REGEXP - regexp passed to ng-annoate
see ng-annotate documentation
NG_OPT - comma separate list of "opt=value" key pairs passed as options to ng-annotate
see ng-annotate documentation
NG_FORCE=true - force ng-annoate processing in development/test environment
Examples,
# Test assets compile in rails development environment
# (assuming config/environments/development.rb is adjusted approriately)
NG_FORCE=true RAILS_ENV=development bundle exec rake assets:clean assets:precompile
The ngannotate-rails version number mirrors the version number for the version of ngannotate that is bundled with it.
-
Q: I installed ngannotate-rails, but my assets aren't getting processed with ngannotate.
A: Remember to delete
tmp/cache/assetsortouchall the related asset files so that the cached versions get regenerated. If you've precompiled your assets intopublic/assets, you'll need to re-precompile them.
The actual ngannotate project is bundled into this gem via Browserify. You can update to the latest version of ngannotate via Rake:
rake ngannotate:build
There is a Rails 3 application bundled in example/ that you can use to test the asset pipeline integration. Don't forget to remove tmp/cache/assets after upgrading to the latest version of ngannotate.
This gem is based into https://github.com/jasonm/ngmin-rails