Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grunt task #193

Open
rombert opened this issue Aug 23, 2019 · 0 comments
Open

Grunt task #193

rombert opened this issue Aug 23, 2019 · 0 comments
Labels

Comments

@rombert
Copy link
Contributor

rombert commented Aug 23, 2019

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:

/shared
  /reveal.js-support
    /package.json
    /gruntfile.shared.js
/2019
  /conf-1
    /pres-1
      /package.json
      /index.html
    /pres-2
      /package.json
      /index.html
  /conf-2
    /pres-3
      /package.json
      /index.html  

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.

  "scripts": {
    "build": "grunt --gruntfile ../../../shared/reveal.js-support/gruntfile.shared.js"
  }

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 :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants