June 25, 2015
With the release of Agent 6, we hit a lot of milestones in our app. Agent became a true Single-page Application, we implemented a global Nav Menu that could be accessed anywhere, we upgraded the infrastructure to the latest version, and many more things. Along with this update, one goal we had was to rethink our frontend automation. At the time, we used a tool called Grunt. This is a node-based task runner. It allows you to define and run tasks that are often repeated in the development process such as compilations, optimizations, file copying, and others. Gulp is also a task automation tool but implemented differently with different objectives that we'll discuss later in this post. The Problem We saw that our gruntfile was getting out of control. It had grown to over 17 separate tasks with some configurations spanning…
From Grunt to Gulp
June 25, 2015
With the release of Agent 6, we hit a lot of milestones in our app. Agent became a true Single-page Application, we implemented a global Nav Menu that could be accessed anywhere, we upgraded the infrastructure to the latest version, and many more things. Along with this update, one goal we had was to rethink our frontend automation. At the time, we used a tool called Grunt. This is a node-based task runner. It allows you to define and run tasks that are often repeated in the development process such as compilations, optimizations, file copying, and others. Gulp is also a task automation tool but implemented differently with different objectives that we'll discuss later in this post. The Problem We saw that our gruntfile was getting out of control. It had grown to over 17 separate tasks with some configurations spanning…