Closed smithje closed 10 years ago
@jonschlinkert we might be able to use _.runInContext()
for this.
I was going to suggest the same. This is why I put the mixins on _.fn
in Phaser (I think I kept that in, need to double check). Speaking of which, this issue is timely in a way (I guess it's never timely have have an issue...).
However, grunt-readme will be powered by Phaser now. we'll also be releasing a grunt-phaser task and gulp-phaser.
@smithje we just pushed it up so it still needs some work, but feedback is welcome.
Closing since this repo has been deprecated. We created a new and improved version of this: Verb, along with grunt and gulp tasks, a cli and a generator. It does what grunt-readme does, but super easy to use (requiring zero config) and waaaay more powerful for anyone who wants more than the defaults. If you like the idea of what grunt-readme does, or should do, please give Verb a look!
The include mixin at line 177 of the readme.js:
overrides underscore's include, which is an alias of _.contains.
I have registered a build task in grunt that is failing because it contains tasks from both grunt-readme and grunt-contrib-compress, which uses _.include. I can run either of these tasks independently, but if I try to run them together, I get this warning:
Unfortunately, grunt-contrib-compress has to come after grunt-readme, because I'm creating a tar of all of my files.
Here's a very minimal example:
package.json:
Gruntfile.js:
Which outputs:
Note the grunt-readme in the stack is being called during the compress task.