Upgrade to Pro — share decks privately, control downloads, hide ads and more …

JavaScript DevOPS - Automating everything JS

Manan
January 24, 2015

JavaScript DevOPS - Automating everything JS

The talk was about front end operations. It talks about the need for automating build tasks and the various means. It also discusses the role of front end operations engineer and how it shouldn't be looked at as a separate role.

This talk was presented at the Bangalore JS meet on Jan 24, '15.

Manan

January 24, 2015
Tweet

More Decks by Manan

Other Decks in Programming

Transcript

  1. • File based • Excellent community support with thousands of

    plugins • Emphasis to configuration over code
  2. • File based • Excellent community support with thousands of

    plugins • Emphasis to configuration over code • Aliases
  3. • File based • Excellent community support with thousands of

    plugins • Emphasis to configuration over code • Aliases • Variables
  4. • File based • Excellent community support with thousands of

    plugins • Emphasis to configuration over code • Aliases • Variables • Can be used as a deployment tool as well
  5. { version: 3, file: "script.js.map", sources: [ "app.js", "content.js", "widget.js"

    ], sourceRoot: "/", names: ["slideUp", "slideDown", "save"], mappings: "AAA0B,kBAAhBA,QAAOC,SACjBD,OAAOC,OAAO..." } Debugging the debuggable http://www.html5rocks.com/en/tutorials/developertools/sourcemaps/
  6. • Stream based • Extremely fast due to reduced I/O.

    Concurrency in-built • Code over configuration
  7. • Stream based • Extremely fast due to reduced I/O.

    Concurrency in-built • Code over configuration • Simple In, Out, Watch API
  8. • Define tasks with gulp.task() • Watch the file system

    for changes with gulp.watch() • Open files/directories with gulp.src()
  9. • Define tasks with gulp.task() • Watch the file system

    for changes with gulp.watch() • Open files/directories with gulp.src() • Output files/directories with gulp.dest()