In the documentation of this Grunt task, maybe it could be clarified that AMD dependencies can be added in two ways:
Including them in the Gruntfile, when they are used by all HAML templates
Including them in the particular template, when they are specific
In addition, the current documentation suggests adding the following line to express a dependency: != require('path/to/other')() (option 2 above). This assumes that the value of the module is a function and that we want to call it. In general, though, the value of the module may be a simple object or even a function that we don't want to call. I would suggest to modify the documentation as follows: != require('path/to/other').
In the documentation of this Grunt task, maybe it could be clarified that AMD dependencies can be added in two ways:
In addition, the current documentation suggests adding the following line to express a dependency:
!= require('path/to/other')()(option 2 above). This assumes that the value of the module is a function and that we want to call it. In general, though, the value of the module may be a simple object or even a function that we don't want to call. I would suggest to modify the documentation as follows:!= require('path/to/other').