Skip to content
Benjamin Arthur Lupton edited this page Jan 14, 2014 · 4 revisions

14 January 2014

Participants: Tyler, Jo, BenA, BenL, Eric

  • Goal: have library authors (like Sass, CoffeeScript) maintain their own plugin that goes into any build tool (grunt, gulp, brunch, etc.)

  • Task Specification

  • Task Complications

    • Sourcemaps
      • Have to be implemented on every single step
    • RequireJS
  • What do we need to agree on?

    • Do we want to do this? (implement the same task spec)
      • BenA: Grunt: Yes!
      • BenL: DocPad: We're happy though, but I'm doubtful of where in DocPad it would be implemented, as we are more than just rendering transforms
  • BenL: Will DocPad interop with node task?

    • Does this make sense to implement?
      • Right now if someone wants to leverage interop, they just install the build system plugin they want, e.g. docpad-plugin-grunt
      • Advantage: less wrappers, interop on the application level
  • Are we all trying to do the same thing? (implementing the same tasks in our own systems)

  • What are the biggest pain points of your current build system?

    • BenA: The grunt team do not have the bandwidth to manage all the issues with our 40+ plugins
    • Tyler: We have to trust people on code we don't know about, are implementing it the right way
      • A: Want to do it; Pro-active
      • B: Will do it; Capable
Clone this wiki locally