It would be useful to have a grunt task for Decktape. I'll describe my scenario below ( which is admittedly a bit exotic ) but on the other hand others may have a use for it as well.
I am generating my presentations using reveal.js and have a single repository for all presentations:
This works pretty well and in general can add a new presentation with minimal boilerplate and only the grunt-cli dev dependency.
Since adding decktape as a dev dependency each presentation has about 340 MB extra in its node_modules directory, which is significant. I would like to avoid that. I have considered using npm install -g decktape, but it's non-portable and polutes the system area.
Adding a decktape grunt task would allow me move the decktape dependency to the shared file.
And I am sure there may be other reasons for using a grunt task as opposed to calling decktape directly :-)
It would be useful to have a grunt task for Decktape. I'll describe my scenario below ( which is admittedly a bit exotic ) but on the other hand others may have a use for it as well.
I am generating my presentations using reveal.js and have a single repository for all presentations:
Each of the presentations has a minimal package.json which calls grunt with the Gruntfile from
/shared/reveal.js-support/gruntfile.shared.js
, e.g.This works pretty well and in general can add a new presentation with minimal boilerplate and only the
grunt-cli
dev dependency.Since adding
decktape
as a dev dependency each presentation has about 340 MB extra in itsnode_modules
directory, which is significant. I would like to avoid that. I have considered usingnpm install -g decktape
, but it's non-portable and polutes the system area.Adding a decktape grunt task would allow me move the decktape dependency to the shared file.
And I am sure there may be other reasons for using a grunt task as opposed to calling decktape directly :-)