Explore topic-wise InterviewSolutions in Current Affairs.

The lists of Plugins are:

• babel - Use next generation JAVASCRIPT, today
• contrib-copy - Copy files and folders.
• benchmark- Grunt task for benchmarking
• bower-clean - Remove files (e.g. docs, tests, etc.) from installed bower components
• watch -Run predefined tasks whenever WATCHED file patterns are added, changed or deleted.
• jshint- Validate files with JSHint
• contrib-requirejs - Optimize RequireJS projects using r.js
• contrib-uglify- Minify files with UglifyJS
• contrib-jade -Compile Jade templates
• concat- Concatenate files.
• css-URL-EMBED- Embed URL's as base64 strings inside your stylesheets
• contrib- Precompile Underscore templates to JST file
• contrib-HTMLmin- Minify HTML
• cssmin- Minify CSS
• contrib-less- Compile LESS files to CSS
• And many more

The lists of Plugins are:

Some of the Advantages of USING Gruntjs:

1.Access too many PREDEFINED plugins that can be used to work with JavaScript TASKS and on static content.

2.All task runners have the following properties: consistency, effectiveness, efficiency, repeatability, etc.

3.Allows USERS to customize tasks using predefined plugins

4.Prefers the configuration approach to coding

5.Allows users to add their own plugins and PUBLISH them to npm.

Some of the Advantages of using Gruntjs:

1.Access too many predefined plugins that can be used to work with JavaScript tasks and on static content.

2.All task runners have the following properties: consistency, effectiveness, efficiency, repeatability, etc.

3.Allows users to customize tasks using predefined plugins

4.Prefers the configuration approach to coding

5.Allows users to add their own plugins and publish them to npm.

Yes, this can be DONE. This APPROACH helps DEVELOPER's LOTS of time.

Yes, this can be done. This approach helps developer's lots of time.

YES, it can SIMPLY be DONE.

Yes, it can simply be done.

Grunt has become very POPULAR and has tons of plugins to choose from. These plugins are great ASSETS for any app to automate various THINGS with MINIMUM efforts.

Grunt has become very popular and has tons of plugins to choose from. These plugins are great assets for any app to automate various things with minimum efforts.

The multiple Steps INVOLVES to install and use Grunt.js:

• Install Node.js and Grunt.
• Create package.json and list dependencies (Grunt and plugins).
• Install NPM MODULES.
• Create Gruntfile.js.
• CONFIGURE tasks you need to run.
• Run those tasks in the COMMAND line while you work.

The multiple Steps involves to install and use Grunt.js:

A task runner can do most of your WORKS with zero EFFORT. All task runners have the following PROPERTIES:

• Consistency
• Effectiveness
• EFFICIENCY
• Repeatability
• and so on

A task runner can do most of your works with zero effort. All task runners have the following properties:

• Grunt js is a JavaScript task RUNNER and it used to automate tasks like magnification, compilation, concat, unit testing, and CHECKING js errors. It uses CLI (Command Line Interface) to run custom tasks.
• Grunt js was created by Ben Alman and Gruntjs is written in Node.js in Sept 2016.
• Grunt js is basically a helping TOOL that main aims to cut down the code. Basically, it is used when there is a need to call the functional or similar tasks again and again.
• There were more than 6,000 plugins available in the Grunt ecosystem.
• Companies that use Gruntjs - Adobe Systems, jQuery, Twitter, Mozilla, Bootstrap, Cloudant, Opera, WordPress, Walmart, and MICROSOFT.

Though there are tons of PLUGINS which you can use, but below are the most used.

• watch: RUN predefined tasks whenever watched file PATTERNS are added, changed or deleted.
• jshint: Validate files with JSHint
• uglify: Minify files with UglifyJS
• concat: Concatenate files.
• cssmin: Minify CSS
• less: Compile LESS files to CSS.

Below is a sample gruntfile.JS for your reference.

1. module.exports = function(grunt) {
2. grunt.initConfig({
3. pkg: grunt.file.readJSON('package.json'),
4. concat: {
5. options: {
6. separator: ';'
7. },
8. dist: {
9. src: ['src/**/*.js'],
10. dest: 'dist/<%= pkg.name %>.js'
11. }
12. },
13. uglify: {
14. options: {
15. BANNER: '/*! <%= pkg.name %> <%= grunt.template.today("dd-mm-yyyy") %> */n'
16. },
17. dist: {
18. files: {
19. 'dist/<%= pkg.name %>.min.js': ['<%= concat.dist.dest %>']
20. }
21. }
22. },
23. jshint: {
24. files: ['Gruntfile.js', 'src/**/*.js', 'test/**/*.js'],
25. options: {
26. // options here to override JSHint defaults
27. globals: {
28. jQuery: true,
29. console: true,
30. module: true,
31. document: true
32. }
33. }
34. }
35. });
36. grunt.loadNpmTasks('grunt-contrib-uglify');
37. grunt.loadNpmTasks('grunt-contrib-jshint');
38. grunt.loadNpmTasks('grunt-contrib-concat');
39. grunt.registerTask('test', ['jshint']);
40. grunt.registerTask('default', ['jshint', 'concat', 'uglify']);
41. };

Though there are tons of plugins which you can use, but below are the most used.

Below is a sample gruntfile.js for your reference.

USE the --STACK OPTION to see stack TRACES. Such as GRUNT task –stack.

Use the --stack option to see stack traces. Such as grunt task –stack.

Every grunt module MAY have defined a task. But running them individually can make things difficult for developers. What is one wants to run grunt uglify and grunt jshint together

Using grunt.registerTask(taskName, [description, ] taskList) we can group all the tasks under one roof. Task NAME can be anything of your choice, description is optional and task list is array of module tasks which you wish to execute. For example,

grunt.registerTask('development', ['jshint:development', 'concat:development', 'uglify:development']);

Above code creates a task named “development” and is asked to execute development target of “jshint”, “concat” and “uglify” packages. Similarly, you can register another task for PRODUCTION VERSION.

grunt.registerTask('production', ['jshint:production', 'concat:production', 'uglify:production']);

Remember, you always need to define a default task.

grunt.registerTask('default', ['jshint', 'uglify', 'concat']);

Now, when you enter grunt on command prompt, it will execute the default task.

Every grunt module may have defined a task. But running them individually can make things difficult for developers. What is one wants to run grunt uglify and grunt jshint together

Using grunt.registerTask(taskName, [description, ] taskList) we can group all the tasks under one roof. Task name can be anything of your choice, description is optional and task list is array of module tasks which you wish to execute. For example,

grunt.registerTask('development', ['jshint:development', 'concat:development', 'uglify:development']);

Above code creates a task named “development” and is asked to execute development target of “jshint”, “concat” and “uglify” packages. Similarly, you can register another task for production version.

grunt.registerTask('production', ['jshint:production', 'concat:production', 'uglify:production']);

Remember, you always need to define a default task.

grunt.registerTask('default', ['jshint', 'uglify', 'concat']);

Now, when you enter grunt on command prompt, it will execute the default task.

GRUNT.loadNpmTasks() is used for LOADING grunt plugins. Before loading, please ensure that these plugins are ALREADY installed VIA NPM.

grunt.loadNpmTasks('grunt-contrib-uglify');

grunt.loadNpmTasks() is used for loading grunt plugins. Before loading, please ensure that these plugins are already installed via npm.

grunt.loadNpmTasks('grunt-contrib-uglify');

You can execute the grunt TASK from COMMAND line. Remember, we have grunt command line INTERFACE. To execute contact MODULE with grunt for all the tasks.

grunt CONCAT

To execute task with particular target

grunt concat:development

You can execute the grunt task from command line. Remember, we have grunt command line interface. To execute contact module with grunt for all the tasks.

grunt concat

To execute task with particular target

grunt concat:development

Tasks are grunt’s bread and butter. Every time Grunt is run, you specify one or more tasks to run, which tells Grunt what you’d like it to do. See below code.

1. grunt.initConfig({
2. concat: {
3. development: {
4. // concat task "development" target options and files go here.
5. },
6. PRODUCTION: {
7. // concat task "production" target options and files go here.
8. },
9. },
10. uglify: {
11. development: {
12. // uglify task "development" target options and files go here.
13. },
14. },
15. });

Here, there are 2 tasks DEFINED concat and uglify. And for each task, we defined TARGETS. For concat, there are 2 targets “development” and “production” and only “development” for uglify. Creating target allows us to define separate settings for different objectives. Here, we can have different option for development and production version. It’s not COMPULSORY to define a target.

Target’s can also have their own option parameters which will OVERRIDE the settings of options defined for the task.

Tasks are grunt’s bread and butter. Every time Grunt is run, you specify one or more tasks to run, which tells Grunt what you’d like it to do. See below code.

Here, there are 2 tasks defined concat and uglify. And for each task, we defined targets. For concat, there are 2 targets “development” and “production” and only “development” for uglify. Creating target allows us to define separate settings for different objectives. Here, we can have different option for development and production version. It’s not compulsory to define a target.

Target’s can also have their own option parameters which will override the settings of options defined for the task.

Yes, we can override. Inside a TASK configuration, an options property MAY be SPECIFIED to override built-in defaults. In ADDITION, each target may have an options property which is specific to that target.

1. module.exports = function(grunt) {
2. grunt.initConfig({
3. pkg: grunt.file.readJSON('package.json'),
4. concat: {
5. options: {
6. SEPARATOR: ';'
7. }
8. }
9. });
10. };

Yes, we can override. Inside a task configuration, an options property may be specified to override built-in defaults. In addition, each target may have an options property which is specific to that target.

GRUNT plugin configuration needs to be DEFINED within grunt.initConfig method. See below sample CODE.

1. module.exports = function(grunt) {
2. grunt.initConfig({
3. pkg: grunt.file.readJSON('package.json'),
4. concat: {
5. // concat TASK configuration GOES here.
6. },
7. uglify: {
8. // uglify task configuration goes here.
9. }
10. });
11. };

Above code configures concat and uglify tasks.

Grunt plugin configuration needs to be defined within grunt.initConfig method. See below sample code.

Above code configures concat and uglify tasks.

Task configuration is specified in your Gruntfile via the grunt.initConfig method. Inside of grunt.initConfig(), we READ the information from package.json and SAVED it to a pkg PROPERTY. With this, we can use the attributes from our package.json file. We can call the name of our PROJECT using pkg.name and the version with pkg.version.

1. module.exports = function(grunt) {
2. grunt.initConfig({
3. pkg: grunt.file.readJSON('package.json')
4. });
5. };

Task configuration is specified in your Gruntfile via the grunt.initConfig method. Inside of grunt.initConfig(), we read the information from package.json and saved it to a pkg property. With this, we can use the attributes from our package.json file. We can call the name of our project using pkg.name and the version with pkg.version.

GRUNT cli is COMMAND line interface to run grunt commands. In other words, it’s a tool to access Grunt from command line anywhere in the system. To INSTALL, grunt –cli execute following command

npm install -g grunt-cli

This will put the grunt command in your system path, allowing it to be run from any directory. Please note, that installing grunt-cli, doesn’t install grunt on your system.

-g MEANS global which means it adds to PATH variables of the system so that you can run grunt from anywhere (without going to specific FOLDER on command prompt).

The reason for having two components is to ensure that we can run different grunt versions side-by-side (i.e. legacy versions in older projects). Hence it is recommended to install grunt-cli globally while grunt should be installed on a per-project basis.

Grunt cli is command line interface to run grunt commands. In other words, it’s a tool to access Grunt from command line anywhere in the system. To install, grunt –cli execute following command

npm install -g grunt-cli

This will put the grunt command in your system path, allowing it to be run from any directory. Please note, that installing grunt-cli, doesn’t install grunt on your system.

-g means global which means it adds to PATH variables of the system so that you can run grunt from anywhere (without going to specific folder on command prompt).

The reason for having two components is to ensure that we can run different grunt versions side-by-side (i.e. legacy versions in older projects). Hence it is recommended to install grunt-cli globally while grunt should be installed on a per-project basis.

Run following command to UNINSTALL grunt.

1. NPM uninstall grunt

And if you wish to remove it from package.json, then USE --save-dev OPTION.

1. npm uninstall --save-dev grunt

Run following command to uninstall grunt.

And if you wish to remove it from package.json, then use --save-dev option.

The syntax REMAINS name but the only thing which changes is module/plugin name.

1. NPM INSTALL --save-dev

For example, to install UGLIFY plugin:

1. npm install grunt-contrib-uglify --save-dev

By default, it always installs the latest version available. But if you wish to install SPECIFIC version then same you can include in the command.

1. npm install @version --save-dev

The syntax remains name but the only thing which changes is module/plugin name.

For example, to install uglify plugin:

By default, it always installs the latest version available. But if you wish to install specific version then same you can include in the command.

Grunt modules are distributed through Node’s NPM DIRECTORY. NORMALLY, they are prefixed with grunt- and OFFICIAL grunt plugins are prefixed with grunt-contrib. Example: grunt-contrib-uglify. You can get list of all grunt plugins here.

Grunt modules are distributed through Node’s NPM directory. Normally, they are prefixed with grunt- and official grunt plugins are prefixed with grunt-contrib. Example: grunt-contrib-uglify. You can get list of all grunt plugins here.

In the simplest TERMS, the tilde matches the most recent minor version (the middle NUMBER). ~1.2.3 will match all 1.2.x versions but will MISS 1.3.0. The caret, on the other HAND, is more relaxed. It will update you to the most recent major version (the first number). ^1.2.3 will match any 1.x.x release INCLUDING 1.3.0, but will hold off on 2.0.0.

You can also define the exact version number that you wish to use like “1.3.5” or to always use latest version, simply use latest or *.

In the simplest terms, the tilde matches the most recent minor version (the middle number). ~1.2.3 will match all 1.2.x versions but will miss 1.3.0. The caret, on the other hand, is more relaxed. It will update you to the most recent major version (the first number). ^1.2.3 will match any 1.x.x release including 1.3.0, but will hold off on 2.0.0.

You can also define the exact version number that you wish to use like “1.3.5” or to always use latest version, simply use latest or *.

Before will look at the difference, it is IMPORTANT to understand the difference between dependencies and devDependencies.

devDependencies are for the development-related scripts, e.g. unit testing, packaging scripts, DOCUMENTATION generation, etc. where dependencies are required for production USE, and assumed required for dev as well. As for example, you can include some plugin which you require during development like (for debugging or unit testing) but you don’t need them on production.

So --save adds packages under dependencies and --save-dev adds under devdependencies SECTION.

1. {
2. "name": "my-project-name",
3. "version": "0.1.0",
4. "dependencies": {
5. "grunt": "~0.4.5",
6. "grunt-contrib-nodeunit": "~0.4.1",
7. "grunt-contrib-uglify": "~0.5.0"
8. }
9. "devDependencies": {
10. "grunt": "~0.4.5",
11. "grunt-contrib-jshint": "~0.10.0",
12. }
13. }

Before will look at the difference, it is important to understand the difference between dependencies and devDependencies.

devDependencies are for the development-related scripts, e.g. unit testing, packaging scripts, documentation generation, etc. where dependencies are required for production use, and assumed required for dev as well. As for example, you can include some plugin which you require during development like (for debugging or unit testing) but you don’t need them on production.

So --save adds packages under dependencies and --save-dev adds under devdependencies section.

As mentioned in previous ANSWER that “package.json” file holds the METADATA for grunt plugins. So when grunt is installed USING --save-dev option, the metadata is added to package.json. So you don’t have to add it manually. And this is how your package.json will look LIKE,

1. {
2. "NAME": "my-project-name",
3. "version": "0.1.0",
4. "devDependencies": {
5. "grunt": "~0.4.5",
6. "grunt-contrib-jshint": "~0.10.0",
7. "grunt-contrib-nodeunit": "~0.4.1",
8. "grunt-contrib-uglify": "~0.5.0"
9. }
10. }

As mentioned in previous answer that “package.json” file holds the metadata for grunt plugins. So when grunt is installed using --save-dev option, the metadata is added to package.json. So you don’t have to add it manually. And this is how your package.json will look like,

Once INSTALLED, you need to add 2 files to setup Grunt.

1. package.json: This file is used by NPM to store metadata for projects published as npm modules. So basically, there will be list of all Grunt plugins, along with grunt which your project is using.

2. Gruntfile: This file is NAMED Gruntfile.js and is used to CONFIGURE or define tasks and load Grunt plugins.

Once installed, you need to add 2 files to setup Grunt.

1. package.json: This file is used by npm to store metadata for projects published as npm modules. So basically, there will be list of all Grunt plugins, along with grunt which your project is using.

2. Gruntfile: This file is named Gruntfile.js and is used to configure or define tasks and load Grunt plugins.

GRUNT and Grunt plugins are installed and managed via npm, the Node.js PACKAGE manager. To install grunt, first ENSURE the npm is installed properly. And then run following COMMAND.

1. npm install grunt --save-dev

PLEASE note, --save-dev is optional.

Grunt and Grunt plugins are installed and managed via npm, the Node.js package manager. To install grunt, first ensure the npm is installed properly. And then run following command.

Please note, --save-dev is optional.

GRUNT has BECOME very popular and has tons of plugins to choose from. These plugins are great assets for any APP to AUTOMATE various THINGS with minimum efforts.

Grunt has become very popular and has tons of plugins to choose from. These plugins are great assets for any app to automate various things with minimum efforts.

Grunt is a JAVASCRIPT TASK runner, which can automate tasks like minification, compilation, UNIT testing, CHECKING js errors. Once CONFIGURED, one doesn’t have to worry about these tasks.

Grunt is a JavaScript task runner, which can automate tasks like minification, compilation, unit testing, checking js errors. Once configured, one doesn’t have to worry about these tasks.