Excellent, Chris! Some people fear GruntJS due to the terminal/cli, but the ways to configure these guys becomes more friendly through some practical procedures.
Also:
* We can use “npm init” to create a file “package.json” based on some answers;
* and conduct a preliminary search to find out which plugins are needed and then run “npm i (alias for install) grunt-contrib-sass grunt-contrib-uglify grunt-contrib-jshint grunt-contrib-watch —save-dev” to install these guys more efficiently and list them into “package.json”.
Vitor Britto
Excellent, Chris! Some people fear GruntJS due to the terminal/cli, but the ways to configure these guys becomes more friendly through some practical procedures.
Also:
* We can use “npm init” to create a file “package.json” based on some answers;
* and conduct a preliminary search to find out which plugins are needed and then run “npm i (alias for install) grunt-contrib-sass grunt-contrib-uglify grunt-contrib-jshint grunt-contrib-watch —save-dev” to install these guys more efficiently and list them into “package.json”.