Question: In my Rails app, there is a method defined in the ApplicationController that I need to use in a module. This module also needs to be accessible to all controllers/helpers. I'm not sure what the best way is to give the module access to this method. I figure that there is a way to do it by wrapping the module and then including it into the ApplicationController. 

I also want to retain the namespacing instead of including the module methods right into the controller. e.g. controller.Module.foo instead of just controller.foo

This is what I'm trying to do:

```
module Analytics
  module Events
    extend self

    def create_event name
      # do some stuff
      controller_method name
    end
  end
end

class ApplicationController < ActionController::Base
  include Analytics

  def controller_method
     # ...
  end

  def some_other_method
    Events.create_event :test
  end
end

```

Now I know I can add a self.included method to the Analytics module which gives me the passed in base object, but I don't know how I can make use of that base in the KissMetrics module.

Is this possible or is there a better way of doing this?

Edit:
-----

To further clarify, I am using a gem that is extended/included into ActionController::Base. See bottom of this [script](https://github.com/jkrall/analytical/blob/master/lib/analytical.rb). This library is then configured inside the ApplicationController. All I want to do is have a module with defined events that makes use of this gem. It makes it easier for me to have consistent events across all my controllers e.g.

```
module Events
  def sign_up_event
    analytical.event "sign up" # calls the library that was loaded into the app controller
  end
end

# in some controller
Events.sign_up_event
# instead of this, which is totally usable but not DRY
analytical.event "sign up"

```

Answer: 
It was a bug caused by a change in Node 0.10.0, and was [fixed](https://github.com/gruntjs/grunt/commit/c6f83ca060e46a0e94160cd64e57cc80aa23917d) earlier today. Will be released soon.
if you're using 'bower'(A package manager for the web), I had the same issue, It turned that its a bower library error when try to install angular. I run the bower build separately like below

```
bower install angular

```

Then I selected the correct version, and it works for me.