Node.

js

i
 [Link]

About the Tutorial

[Link] is a very powerful JavaScript-based framework/platform built on Google Chrome's
JavaScript V8 Engine. It is used to develop I/O intensive web applications like video
streaming sites, single-page applications, and other web applications. [Link] is open
source, completely free, and used by thousands of developers around the world.

Audience
This tutorial is designed for software programmers who want to learn the basics of [Link]
and its architectural concepts. This tutorial will give you enough understanding on all the
necessary components of [Link] with suitable examples.

Prerequisites
Before proceeding with this tutorial, you should have a basic understanding of JavaScript.
As we are going to develop web-based applications using [Link], it will be good if you
have some understanding of other web technologies such as HTML, CSS, AJAX, etc.

Execute [Link] Online

For most of the examples given in this tutorial, you will find a Try it option, so just make
use of this option to execute your [Link] programs on the spot and enjoy your learning.

Try the following example using the Try it option available at the top right corner of the
below sample code box (on our website):

/* Hello World! program in [Link] */

[Link]("Hello World!");

Copyright & Disclaimer

 Copyright 2016 by Tutorials Point (I) Pvt. Ltd.

All the content and graphics published in this e-book are the property of Tutorials Point (I)
Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or republish
any contents or a part of contents of this e-book in any manner without written consent
of the publisher.

We strive to update the contents of our website and tutorials as timely and as precisely as
possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt.
Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our
website or its contents including this tutorial. If you discover any errors on our website or
in this tutorial, please notify us at contact@[Link]

i
 [Link]

Table of Contents
About the Tutorial ............................................................................................................................................ i
Audience ........................................................................................................................................................... i
Prerequisites ..................................................................................................................................................... i
Execute [Link] Online..................................................................................................................................... i
Copyright & Disclaimer ..................................................................................................................................... i
Table of Contents ............................................................................................................................................ ii

1. Introduction .............................................................................................................................................. 1
What is [Link]? .............................................................................................................................................. 1
Features of [Link] ......................................................................................................................................... 1
Who Uses [Link]? .......................................................................................................................................... 2
Concepts .......................................................................................................................................................... 2
Where to Use [Link]? .................................................................................................................................... 2
Where Not to Use [Link]? ............................................................................................................................. 2

2. Environment Setup ................................................................................................................................... 3

Try it Option Online ......................................................................................................................................... 3
Local Environment Setup ................................................................................................................................. 3
Text Editor ....................................................................................................................................................... 3
The [Link] Runtime ....................................................................................................................................... 3
Download [Link] Archive .............................................................................................................................. 4
Installation on UNIX/Linux/Mac OS X and SunOS............................................................................................ 4
Installation on Windows .................................................................................................................................. 4
Verify Installation: Executing a File.................................................................................................................. 5

3. First Application ........................................................................................................................................ 6

Creating [Link] Application ........................................................................................................................... 6

4. REPL Terminal ........................................................................................................................................... 9

Online REPL Terminal ...................................................................................................................................... 9
REPL Commands ............................................................................................................................................ 11
Stopping REPL ................................................................................................................................................ 11

5. NPM........................................................................................................................................................ 12
Installing Modules using NPM ....................................................................................................................... 12
Global vs Local Installation ............................................................................................................................ 12
Using [Link] ........................................................................................................................................ 14
Attributes of [Link] ............................................................................................................................. 19
Uninstalling a Module ................................................................................................................................... 19
Updating a Module ........................................................................................................................................ 19
Search a Module ............................................................................................................................................ 19
Create a Module ............................................................................................................................................ 19

6. Callback Concept ..................................................................................................................................... 21

What is Callback?........................................................................................................................................... 21
Blocking Code Example.................................................................................................................................. 21
Non-Blocking Code Example.......................................................................................................................... 22

ii
 [Link]

7. Event Loop .............................................................................................................................................. 23

Event-Driven Programming ........................................................................................................................... 23
Example ......................................................................................................................................................... 24
How Node Applications Work? ..................................................................................................................... 25

8. Event Emitter .......................................................................................................................................... 26

EventEmitter Class ......................................................................................................................................... 26
Methods ........................................................................................................................................................ 26
Class Methods ............................................................................................................................................... 27
Events ............................................................................................................................................................ 28
Example ......................................................................................................................................................... 28

9. Buffers .................................................................................................................................................... 30
Creating Buffers ............................................................................................................................................. 30
Writing to Buffers .......................................................................................................................................... 30
Reading from Buffers ..................................................................................................................................... 31
Convert Buffer to JSON .................................................................................................................................. 32
Concatenate Buffers ...................................................................................................................................... 33
Compare Buffers ............................................................................................................................................ 33
Copy Buffer .................................................................................................................................................... 34
Slice Buffer..................................................................................................................................................... 35
Buffer Length ................................................................................................................................................. 36
Methods Reference ....................................................................................................................................... 36
Class Methods ............................................................................................................................................... 41

10. Streams................................................................................................................................................... 43
What are Streams? ........................................................................................................................................ 43
Reading from a Stream .................................................................................................................................. 43
Writing to a Stream ....................................................................................................................................... 44
Piping the Streams......................................................................................................................................... 45
Chaining the Streams..................................................................................................................................... 46

11. File System .............................................................................................................................................. 48

Synchronous vs Asynchronous ...................................................................................................................... 48
Open a File ..................................................................................................................................................... 49
Get File Information ...................................................................................................................................... 51
Writing a File ................................................................................................................................................. 53
Reading a File................................................................................................................................................. 54
Closing a File .................................................................................................................................................. 56
Truncate a File ............................................................................................................................................... 57
Delete a File ................................................................................................................................................... 59
Create a Directory ......................................................................................................................................... 60
Read a Directory ............................................................................................................................................ 61
Remove a Directory ....................................................................................................................................... 62
Methods Reference ....................................................................................................................................... 63

12. Global Objects ........................................................................................................................................ 69

__filename ..................................................................................................................................................... 69
__dirname ..................................................................................................................................................... 69
setTimeout(cb, ms) ........................................................................................................................................ 70
clearTimeout (t) ............................................................................................................................................. 70
setInterval(cb, ms) ......................................................................................................................................... 71
Global Objects ............................................................................................................................................... 71
iii
 [Link]

Console Object .............................................................................................................................................. 72

Process Object ............................................................................................................................................... 74

13. Utility Modules ....................................................................................................................................... 81

OS Module ..................................................................................................................................................... 81
Path Module .................................................................................................................................................. 83
Net Module.................................................................................................................................................... 85
DNS Module................................................................................................................................................... 92
Domain Module ............................................................................................................................................. 95

14. Web Module ........................................................................................................................................... 99

What is a Web Server? .................................................................................................................................. 99
Web Application Architecture ....................................................................................................................... 99
Creating a Web Server using Node .............................................................................................................. 100
Make a request to [Link] server ............................................................................................................... 102
Creating a Web client using Node ............................................................................................................... 102

15. Express Framework ............................................................................................................................... 104

Express Overview ........................................................................................................................................ 104
Installing Express ......................................................................................................................................... 104
Hello world Example .................................................................................................................................... 104
Request & Response .................................................................................................................................... 106
Request Object ............................................................................................................................................ 106
Response Object .......................................................................................................................................... 109
Basic Routing ............................................................................................................................................... 115
Serving Static Files ....................................................................................................................................... 118
GET Method ................................................................................................................................................. 119
POST Method............................................................................................................................................... 121
File Upload ................................................................................................................................................... 123
Cookies Management .................................................................................................................................. 125

16. RESTful API ........................................................................................................................................... 126

What is REST Architecture? ......................................................................................................................... 126
HTTP methods ............................................................................................................................................. 126
RESTful Web Services .................................................................................................................................. 126
Creating RESTful for a Library ...................................................................................................................... 126
List Users ..................................................................................................................................................... 128
Add Users .................................................................................................................................................... 129
Show Detail .................................................................................................................................................. 130
Delete a User ............................................................................................................................................... 131

17. Scaling an Application ........................................................................................................................... 133

The exec() method....................................................................................................................................... 133
The spawn() Method ................................................................................................................................... 135
The fork() Method ....................................................................................................................................... 137

18. Packaging .............................................................................................................................................. 139

JXcore Installation ....................................................................................................................................... 139
Packaging the Code ..................................................................................................................................... 140
Launching JX File .......................................................................................................................................... 140

iv
 1. INTRODUCTION [Link]

What is [Link]?
[Link] is a server-side platform built on Google Chrome's JavaScript Engine (V8 Engine).
[Link] was developed by Ryan Dahl in 2009 and its latest version is v0.10.36. The definition
of [Link] as supplied by its official documentation is as follows:

[Link] is a platform built on Chrome's JavaScript runtime for easily building fast and
scalable network applications. [Link] uses an event-driven, non-blocking I/O model
that makes it lightweight and efficient, perfect for data-intensive real-time applications
that run across distributed devices.

[Link] is an open source, cross-platform runtime environment for developing server-side

and networking applications. [Link] applications are written in JavaScript, and can be run
within the [Link] runtime on OS X, Microsoft Windows, and Linux.

[Link] also provides a rich library of various JavaScript modules which simplifies the
development of web applications using [Link] to a great extent.

[Link] = Runtime Environment + JavaScript Library

Features of [Link]
Following are some of the important features that make [Link] the first choice of software
architects.

 Asynchronous and Event Driven − All APIs of [Link] library are asynchronous,
that is, non-blocking. It essentially means a [Link] based server never waits for an
API to return data. The server moves to the next API after calling it and a notification
mechanism of Events of [Link] helps the server to get a response from the previous
API call.

 Very Fast − Being built on Google Chrome's V8 JavaScript Engine, [Link] library is
very fast in code execution.

 Single Threaded but Highly Scalable − [Link] uses a single threaded model with
event looping. Event mechanism helps the server to respond in a non-blocking way
and makes the server highly scalable as opposed to traditional servers which create
limited threads to handle requests. [Link] uses a single threaded program and the
same program can provide service to a much larger number of requests than
traditional servers like Apache HTTP Server.

5
 [Link]

 No Buffering − [Link] applications never buffer any data. These applications simply
output the data in chunks.

 License − [Link] is released under the MIT license.

Who Uses [Link]?

Following is the link on github wiki containing an exhaustive list of projects, application and
companies which are using [Link]. This list includes eBay, General Electric, GoDaddy,
Microsoft, PayPal, Uber, Wikipins, Yahoo!, and Yammer to name a few.

 Projects, Applications, and Companies Using Node

Concepts
The following diagram depicts some important parts of [Link] which we will discuss in detail
in the subsequent chapters.

Where to Use [Link]?

Following are the areas where [Link] is proving itself as a perfect technology partner.
6
 [Link]

● I/O bound Applications

● Data Streaming Applications
● Data Intensive Real-time Applications (DIRT)
● JSON APIs based Applications
● Single Page Applications

Where Not to Use [Link]?

It is not advisable to use [Link] for CPU intensive applications.

7
 2. ENVIRONMENT SETUP [Link]

Try it Option Online

You really do not need to set up your own environment to start learning [Link]. Reason is
very simple, we already have set up [Link] environment online, so that you can execute all
the available examples online and learn through practice. Feel free to modify any example
and check the results with different options.

Try the following example using the Try it option available at the top right corner of the below
sample code box (on our website):

/* Hello World! program in [Link] */

[Link]("Hello World!");

For most of the examples given in this tutorial, you will find a Try it option, so just make use
of it and enjoy your learning.

Local Environment Setup

If you want to set up your environment for [Link], you need to have the following two
software on your computer, (a) a Text Editor and (b) the [Link] binary installables.

Text Editor
You need to have a text editor to type your program. Examples of text editors include Windows
Notepad, OS Edit command, Brief, Epsilon, EMACS, and vim or vi.

The name and version of text editors can vary from one operating system to another. For
example, Notepad will be used on Windows, and vim or vi can be used on Windows as well as
Linux or UNIX.

The files you create with your editor are called source files and they contain the program
source code. The source files for [Link] programs are typically named with the extension
".js".

Before you start programming, make sure you have one text editor in place and you have
enough experience in how to write a computer program, save it in a file, and finally execute
it.

8
 [Link]

The [Link] Runtime

The source code that you would write in a source file is simply javascript. The [Link]
interpreter interprets and executes your javascript code.

[Link] distribution comes as a binary installable for SunOS, Linux, Mac OS X, and Windows
operating systems with the 32-bit (386) and 64-bit (amd64) x86 processor architectures.

The following section explains how to install [Link] binary distribution on various OS.

Download [Link] Archive

Download the latest version of [Link] installable archive file from [Link] Downloads. At the
time of writing this tutorial, following are the versions available on different OS.

OS Archive name

Windows [Link]

Linux [Link]

Mac [Link]

SunOS [Link]

Installation on UNIX/Linux/Mac OS X and SunOS

Based on your OS architecture, download and extract the archive node-v0.12.0-
[Link] into /tmp, and then move the extracted files into /usr/local/nodejs directory.
For example:

$ cd /tmp
$ wget [Link]
$ tar xvfz [Link]
$ mkdir -p /usr/local/nodejs
$ mv node-v6.3.1-linux-x64/* /usr/local/nodejs

Add /usr/local/nodejs/bin to the PATH environment variable.

OS Output

Linux export PATH=$PATH:/usr/local/nodejs/bin

9
 [Link]

Mac export PATH=$PATH:/usr/local/nodejs/bin

FreeBSD export PATH=$PATH:/usr/local/nodejs/bin

Installation on Windows
Use the MSI file and follow the prompts to install [Link]. By default, the installer uses the
[Link] distribution in C:\Program Files\nodejs. The installer should set the C:\Program
Files\nodejs\bin directory in Window's PATH environment variable. Restart any open
command prompts for the change to take effect.

Verify Installation: Executing a File

Create a js file named [Link] on your machine (Windows or Linux) having the following code.

/* Hello, World! program in [Link] */

[Link]("Hello, World!")

Now execute [Link] using [Link] interpreter to see the result:

$ node [Link]

If everything is fine with your installation, it should produce the following result:

Hello, World!

10
 3. FIRST APPLICATION [Link]

Before creating an actual "Hello, World!" application using [Link], let us see the components
of a [Link] application. A [Link] application consists of the following three important
components:

1. Import required modules: We use the require directive to load [Link] modules.

2. Create server: A server which will listen to client's requests similar to Apache HTTP
Server.

3. Read request and return response: The server created in an earlier step will read
the HTTP request made by the client which can be a browser or a console and return
the response.

Creating [Link] Application

Step 1 - Import Required Module

We use the require directive to load the http module and store the returned HTTP instance
into an http variable as follows:

var http = require("http");

Step 2 - Create Server

We use the created http instance and call [Link]() method to create a server
instance and then we bind it at port 8081 using the listen method associated with the server
instance. Pass it a function with parameters request and response. Write the sample
implementation to always return "Hello World".

[Link](function (request, response) {

// Send the HTTP header

// HTTP Status: 200 : OK
// Content Type: text/plain
[Link](200, {'Content-Type': 'text/plain'});

// Send the response body as "Hello World"

11
 [Link]

[Link]('Hello World\n');
}).listen(8081);

// Console will print the message

[Link]('Server running at [Link]

The above code is enough to create an HTTP server which listens, i.e., waits for a request
over 8081 port on the local machine.

Step 3 - Testing Request & Response

Let's put step 1 and 2 together in a file called [Link] and start our HTTP server as shown
below:

var http = require("http");

[Link](function (request, response) {

// Send the HTTP header

// HTTP Status: 200 : OK
// Content Type: text/plain
[Link](200, {'Content-Type': 'text/plain'});

// Send the response body as "Hello World"

[Link]('Hello World\n');
}).listen(8081);

// Console will print the message

[Link]('Server running at [Link]

Now execute the [Link] to start the server as follows:

$ node [Link]

Verify the Output. Server has started.

Server running at [Link]

12
 [Link]

Make a Request to the [Link] Server

Open [Link] in any browser and observe the following result.

Congratulations, you have your first HTTP server up and running which is responding to all
the HTTP requests at port 8081.

13
 4. REPL TERMINAL [Link]

REPL stands for Read Eval Print Loop and it represents a computer environment like a
Windows console or Unix/Linux shell where a command is entered and the system responds
with an output in an interactive mode. [Link] or Node comes bundled with a REPL
environment. It performs the following tasks:

● Read - Reads user's input, parses the input into JavaScript data-structure, and stores
in memory.

● Eval - Takes and evaluates the data structure.

● Print - Prints the result.

● Loop - Loops the above command until the user presses ctrl-c twice.

The REPL feature of Node is very useful in experimenting with [Link] codes and to debug
JavaScript codes.

Online REPL Terminal

To simplify your learning, we have set up an easy-to-use [Link] REPL environment online,
where you can practice [Link] syntax: Launch [Link] REPL Terminal

Starting REPL
REPL can be started by simply running node on shell/console without any arguments as
follows.

$ node

You will see the REPL Command prompt > where you can type any [Link] command:

$ node
>

Simple Expression
Let's try a simple mathematics at the [Link] REPL command prompt:

$ node
> 1 + 3
14
 [Link]

4
> 1 + ( 2 * 3 ) - 4
3
>

Use Variables
You can make use variables to store values and print later like any conventional script. If var
keyword is not used, then the value is stored in the variable and printed. Whereas if var
keyword is used, then the value is stored but not printed. You can print variables using
[Link]().

$ node
> x = 10
10
> var y = 10
undefined
> x + y
20
> [Link]("Hello World")
Hello Workd
undefined

Multiline Expression
Node REPL supports multiline expression similar to JavaScript. Let's check the following do-
while loop in action:

$ node
> var x = 0
undefined
> do {
... x++;
... [Link]("x: " + x);
... } while ( x < 5 );
x: 1
x: 2
15
 [Link]

x: 3
x: 4
x: 5
undefined
>

... comes automatically when you press Enter after the opening bracket. Node automatically
checks the continuity of expressions.

Underscore Variable
You can use underscore (_) to get the last result:

$ node
> var x = 10
undefined
> var y = 20
undefined
> x + y
30
> var sum = _
undefined
> [Link](sum)
30
undefined
>

REPL Commands
 ctrl + c - terminate the current command.
 ctrl + c twice - terminate the Node REPL.
 ctrl + d - terminate the Node REPL.
 Up/Down Keys - see command history and modify previous commands.
 tab Keys - list of current commands.
 .help - list of all commands.
 .break - exit from multiline expression.

16
 [Link]

 .clear - exit from multiline expression.

 .save filename - save the current Node REPL session to a file.
 .load filename - load file content in current Node REPL session.

Stopping REPL
As mentioned above, you will need to use ctrl-c twice to come out of [Link] REPL.

$ node
>
(^C again to quit)
>

17
 5. NPM [Link]

Node Package Manager (NPM) provides two main functionalities:

 Online repositories for [Link] packages/modules which are searchable on

[Link]

 Command line utility to install [Link] packages, do version management and

dependency management of [Link] packages.

NPM comes bundled with [Link] installables after v0.6.3 version. To verify the same, open
console and type the following command and see the result:

$ npm --version
2.7.1

If you are running an old version of NPM, then it is quite easy to update it to the latest version.
Just use the following command from root:

$ sudo npm install npm -g

/usr/bin/npm -> /usr/lib/node_modules/npm/bin/[Link]
npm@2.7.1 /usr/lib/node_modules/npm

Installing Modules using NPM

There is a simple syntax to install any [Link] module:

$ npm install <Module Name>

For example, following is the command to install a famous [Link] web framework module
called express:

$ npm install express

Now you can use this module in your js file as following:

var express = require('express');

18
 [Link]

Global vs Local Installation

By default, NPM installs any dependency in the local mode. Here local mode refers to the
package installation in node_modules directory lying in the folder where Node application is
present. Locally deployed packages are accessible via require() method. For example, when
we installed express module, it created node_modules directory in the current directory where
it installed the express module.

$ ls -l
total 0
drwxr-xr-x 3 root root 20 Mar 17 02:23 node_modules

Alternatively, you can use npm ls command to list down all the locally installed modules.

Globally installed packages/dependencies are stored in system directory. Such dependencies

can be used in CLI (Command Line Interface) function of any [Link] but cannot be imported
using require() in Node application directly. Now let's try installing the express module using
global installation.

$ npm install express -g

This will produce a similar result but the module will be installed globally. Here, the first line
shows the module version and the location where it is getting installed.

express@4.12.2 /usr/lib/node_modules/express
├── merge-descriptors@1.0.0
├── utils-merge@1.0.0
├── cookie-signature@1.0.6
├── methods@1.1.1
├── fresh@0.2.4
├── cookie@0.1.2
├── escape-html@1.0.1
├── range-parser@1.0.2
├── content-type@1.0.1
├── finalhandler@0.3.3
├── vary@1.0.0
├── parseurl@1.3.0
├── content-disposition@0.5.0
├── path-to-regexp@0.1.3
├── depd@1.0.0
19
 [Link]

├── qs@2.3.3
├── on-finished@2.2.0 (ee-first@1.1.0)
├── etag@1.5.1 (crc@3.2.1)
├── debug@2.1.3 (ms@0.7.0)
├── proxy-addr@1.0.7 (forwarded@0.1.0, [Link]@0.1.9)
├── send@0.12.1 (destroy@1.0.3, ms@0.7.0, mime@1.3.4)
├── serve-static@1.9.2 (send@0.12.2)
├── accepts@1.2.5 (negotiator@0.5.1, mime-types@2.0.10)
└── type-is@1.6.1 (media-typer@0.3.0, mime-types@2.0.10)

You can use the following command to check all the modules installed globally:

$ npm ls -g

Using [Link]
[Link] is present in the root directory of any Node application/module and is used to
define the properties of a package. Let's open [Link] of express package present in
node_modules/express/

{
"name": "express",
"description": "Fast, unopinionated, minimalist web framework",
"version": "4.11.2",
"author": {
"name": "TJ Holowaychuk",
"email": "tj@[Link]"
},
"contributors": [
{
"name": "Aaron Heckmann",
"email": "[Link]+github@[Link]"
},
{
"name": "Ciaran Jessup",
"email": "ciaranj@[Link]"
20
 [Link]

},
{
"name": "Douglas Christopher Wilson",
"email": "doug@[Link]"
},
{
"name": "Guillermo Rauch",
"email": "rauchg@[Link]"
},
{
"name": "Jonathan Ong",
"email": "me@[Link]"
},
{
"name": "Roman Shtylman",
"email": "shtylman+expressjs@[Link]"
},
{
"name": "Young Jae Sim",
"email": "hanul@[Link]"
}
],
"license": "MIT",
"repository": {
"type": "git",
"url": "[Link]
},
"homepage": "[Link]
"keywords": [
"express",
"framework",
"sinatra",
"web",
21
 [Link]

"rest",
"restful",
"router",
"app",
"api"
],
"dependencies": {
"accepts": "~1.2.3",
"content-disposition": "0.5.0",
"cookie-signature": "1.0.5",
"debug": "~2.1.1",
"depd": "~1.0.0",
"escape-html": "1.0.1",
"etag": "~1.5.1",
"finalhandler": "0.3.3",
"fresh": "0.2.4",
"media-typer": "0.3.0",
"methods": "~1.1.1",
"on-finished": "~2.2.0",
"parseurl": "~1.3.0",
"path-to-regexp": "0.1.3",
"proxy-addr": "~1.0.6",
"qs": "2.3.3",
"range-parser": "~1.0.2",
"send": "0.11.1",
"serve-static": "~1.8.1",
"type-is": "~1.5.6",
"vary": "~1.0.0",
"cookie": "0.1.2",
"merge-descriptors": "0.0.2",
"utils-merge": "1.0.0"
},
"devDependencies": {
22
 [Link]

"after": "0.8.1",
"ejs": "2.1.4",
"istanbul": "0.3.5",
"marked": "0.3.3",
"mocha": "~2.1.0",
"should": "~4.6.2",
"supertest": "~0.15.0",
"hjs": "~0.0.6",
"body-parser": "~1.11.0",
"connect-redis": "~2.2.0",
"cookie-parser": "~1.3.3",
"express-session": "~1.10.2",
"jade": "~1.9.1",
"method-override": "~2.3.1",
"morgan": "~1.5.1",
"multiparty": "~4.1.1",
"vhost": "~3.0.0"
},
"engines": {
"node": ">= 0.10.0"
},
"files": [
"LICENSE",
"[Link]",
"[Link]",
"[Link]",
"lib/"
],
"scripts": {
"test": "mocha --require test/support/env --reporter spec --bail –
check-leaks test/ test/acceptance/",

"test-cov": "istanbul cover node_modules/mocha/bin/_mocha -- --

23
 [Link]

require test/support/env --reporter dot --check-leaks test/

test/acceptance/",

"test-tap": "mocha --require test/support/env --reporter tap –

check-leaks test/ test/acceptance/",

"test-travis": "istanbul cover node_modules/mocha/bin/_mocha –

report lcovonly -- --require test/support/env --reporter spec –
check-leaks test/ test/acceptance/"
},
"gitHead": "63ab25579bda70b4927a179b580a9c580b6c7ada",
"bugs": {
"url": "[Link]
},
"_id": "express@4.11.2",
"_shasum": "8df3d5a9ac848585f00a0777601823faecd3b148",
"_from": "express@*",
"_npmVersion": "1.4.28",
"_npmUser": {
"name": "dougwilson",
"email": "doug@[Link]"
},
"maintainers": [
{
"name": "tjholowaychuk",
"email": "tj@[Link]"
},
{
"name": "jongleberry",
"email": "jonathanrichardong@[Link]"
},
{
"name": "shtylman",
24
 [Link]

"email": "shtylman@[Link]"
},
{
"name": "dougwilson",
"email": "doug@[Link]"
},
{
"name": "aredridel",
"email": "aredridel@[Link]"
},
{
"name": "strongloop",
"email": "callback@[Link]"
},
{
"name": "rfeng",
"email": "enjoyjava@[Link]"
}
],
"dist": {
"shasum": "8df3d5a9ac848585f00a0777601823faecd3b148",
"tarball": "[Link]
},
"directories": {},
"_resolved": "[Link]
"readme": "ERROR: No README data found!"
}

Attributes of [Link]
 name - name of the package

 version - version of the package

 description - description of the package

25
 [Link]

 homepage - homepage of the package

 author - author of the package

 contributors - name of the contributors to the package

 dependencies - list of dependencies. NPM automatically installs all the dependencies

mentioned here in the node_module folder of the package.

 repository - repository type and URL of the package

 main - entry point of the package

 keywords - keywords

Uninstalling a Module
Use the following command to uninstall a [Link] module.

$ npm uninstall express

Once NPM uninstalls the package, you can verify it by looking at the content of
/node_modules/ directory or type the following command:

$ npm ls

Updating a Module
Update [Link] and change the version of the dependency to be updated and run the
following command.

$ npm update express

Search a Module
Search a package name using NPM.

$ npm search express

Create a Module
Creating a module requires [Link] to be generated. Let's generate [Link] using
NPM, which will generate the basic skeleton of the [Link].

26
 [Link]

$ npm init
This utility will walk you through creating a [Link] file.
It only covers the most common items, and tries to guess sane defaults.

See 'npm help json' for definitive documentation on these fields

and exactly what they do.

Use 'npm install <pkg> --save' afterwards to install a package and

save it as a dependency in the [Link] file.

Press ^C at any time to quit.

name: (webmaster)

You will need to provide all the required information about your module. You can take help
from the above-mentioned [Link] file to understand the meanings of various
information demanded. Once [Link] is generated, use the following command to
register yourself with NPM repository site using a valid email address.

$ npm adduser
Username: mcmohd
Password:
Email: (this IS public) mcmohd@[Link]

It is time now to publish your module:

$ npm publish

If everything is fine with your module, then it will be published in the repository and will be
accessible to install using NPM like any other [Link] module.

27
 6. CALLBACK CONCEPT [Link]

What is Callback?
Callback is an asynchronous equivalent for a function. A callback function is called at the
completion of a given task. Node makes heavy use of callbacks. All the APIs of Node are
written in such a way that they support callbacks.

For example, a function to read a file may start reading a file and return the control to the
execution environment immediately so that the next instruction can be executed. Once file
I/O is complete, it will call the callback function while passing the callback function, the
content of the file as a parameter. So there is no blocking or wait for File I/O. This makes
[Link] highly scalable, as it can process a high number of requests without waiting for any
function to return results.

Blocking Code Example

Create a text file named [Link] with the following content:

Tutorials Point is giving self learning content

to teach the world in simple and easy way!!!!!

Create a js file named [Link] with the following code:

var fs = require("fs");

var data = [Link]('[Link]');

[Link]([Link]());
[Link]("Program Ended");

Now run the [Link] to see the result:

$ node [Link]

Verify the Output.

Tutorials Point is giving self learning content

28
 [Link]

to teach the world in simple and easy way!!!!!

Program Ended

Non-Blocking Code Example

Create a text file named [Link] with the following content.

Tutorials Point is giving self learning content

to teach the world in simple and easy way!!!!!

Update [Link] to have the following code:

var fs = require("fs");

[Link]('[Link]', function (err, data) {

if (err) return [Link](err);
[Link]([Link]());
});

[Link]("Program Ended");

Now run the [Link] to see the result:

$ node [Link]

Verify the Output.

Program Ended
Tutorials Point is giving self learning content
to teach the world in simple and easy way!!!!!

These two examples explain the concept of blocking and non-blocking calls.

 The first example shows that the program blocks until it reads the file and then only it
proceeds to end the program.

 The second example shows that the program does not wait for file reading and
proceeds to print "Program Ended" and at the same time, the program without blocking
continues reading the file.

29
 [Link]

Thus, a blocking program executes very much in sequence. From the programming point of
view, it is easier to implement the logic but non-blocking programs do not execute in
sequence. In case a program needs to use any data to be processed, it should be kept within
the same block to make it sequential execution.

30
 7. EVENT LOOP [Link]

[Link] is a single-threaded application, but it can support concurrency via the concept of
event and callbacks. Every API of [Link] is asynchronous and being single-threaded, they
use async function calls to maintain concurrency. Node uses observer pattern. Node thread
keeps an event loop and whenever a task gets completed, it fires the corresponding event
which signals the event-listener function to execute.

Event-Driven Programming
[Link] uses events heavily and it is also one of the reasons why [Link] is pretty fast
compared to other similar technologies. As soon as Node starts its server, it simply initiates
its variables, declares functions, and then simply waits for the event to occur.

In an event-driven application, there is generally a main loop that listens for events, and then
triggers a callback function when one of those events is detected.

Although events look quite similar to callbacks, the difference lies in the fact that callback
functions are called when an asynchronous function returns its result, whereas event handling
works on the observer pattern. The functions that listen to events act as Observers.
Whenever an event gets fired, its listener function starts executing. [Link] has multiple in-
built events available through events module and EventEmitter class which are used to bind
events and event-listeners as follows:

// Import events module

var events = require('events');
// Create an eventEmitter object

31
 [Link]

var eventEmitter = new [Link]();

Following is the syntax to bind an event handler with an event:

// Bind event and even handler as follows

[Link]('eventName', eventHandler);

We can fire an event programmatically as follows:

// Fire an event
[Link]('eventName');

Example
Create a js file named [Link] with the following code:

// Import events module

var events = require('events');

// Create an eventEmitter object

var eventEmitter = new [Link]();

// Create an event handler as follows

var connectHandler = function connected() {
[Link]('connection successful.');

// Fire the data_received event

[Link]('data_received');
}

// Bind the connection event with the handler

[Link]('connection', connectHandler);

32
 [Link]

// Bind the data_received event with the anonymous function

[Link]('data_received', function(){
[Link]('data received successfully.');
});

// Fire the connection event

[Link]('connection');

[Link]("Program Ended.");

Now let's try to run the above program and check its output:

$ mnode [Link]

It should produce the following result:

connection successful.
data received successfully.
Program Ended.

How Node Applications Work?

In Node Application, any async function accepts a callback as the last parameter and a
callback function accepts an error as the first parameter. Let's revisit the previous example
again. Create a text file named [Link] with the following content.

Tutorials Point is giving self learning content

to teach the world in simple and easy way!!!!!

Create a js file named [Link] having the following code:

var fs = require("fs");

[Link]('[Link]', function (err, data) {

if (err){
[Link]([Link]);
return;

33
 [Link]

}
[Link]([Link]());
});
[Link]("Program Ended");

Here [Link]() is a async function whose purpose is to read a file. If an error occurs during
the read operation, then the err object will contain the corresponding error, else data will
contain the contents of the file. readFile passes err and data to the callback function after
the read operation is complete, which finally prints the content.

Program Ended
Tutorials Point is giving self learning content
to teach the world in simple and easy way!!!!!

34
 8. EVENT EMITTER [Link]

Many objects in a Node emit events, for example, a [Link] emits an event each time a
peer connects to it, an [Link] emits an event when the file is opened. All objects which
emit events are the instances of [Link].

EventEmitter Class
As we have seen in the previous section, EventEmitter class lies in the events module. It is
accessible via the following code:

// Import events module

var events = require('events');
// Create an eventEmitter object
var eventEmitter = new [Link]();

When an EventEmitter instance faces any error, it emits an 'error' event. When a new listener
is added, 'newListener' event is fired and when a listener is removed, 'removeListener' event
is fired.

EventEmitter provides multiple properties like on and emit. on property is used to bind a
function with the event and emit is used to fire an event.

Methods
[Link]. Method & Description

addListener(event, listener)
Adds a listener at the end of the listeners array for the specified event. No
1 checks are made to see if the listener has already been added. Multiple calls
passing the same combination of event and listener will result in the listener
being added multiple times. Returns emitter, so calls can be chained.

on(event, listener)
Adds a listener at the end of the listeners array for the specified event. No
2 checks are made to see if the listener has already been added. Multiple calls
passing the same combination of event and listener will result in the listener
being added multiple times. Returns emitter, so calls can be chained.

3 once(event, listener)

35
 [Link]

Adds a one-time listener to the event. This listener is invoked only the next time
the event is fired, after which it is removed. Returns emitter, so calls can be
chained.

removeListener(event, listener)

Removes a listener from the listener array for the specified event. Caution: It
4 changes the array indices in the listener array behind the listener. removeListener
will remove, at most, one instance of a listener from the listener array. If any single
listener has been added multiple times to the listener array for the specified event,
then removeListener must be called multiple times to remove each instance.
Returns emitter, so calls can be chained.
removeAllListeners([event])
Removes all listeners, or those of the specified event. It's not a good idea to
5 remove listeners that were added elsewhere in the code, especially when it's on
an emitter that you didn't create (e.g. sockets or file streams). Returns emitter,
so calls can be chained.

setMaxListeners(n)
By default, EventEmitters will print a warning if more than 10 listeners are added
6 for a particular event. This is a useful default which helps finding memory leaks.
Obviously not all Emitters should be limited to 10. This function allows that to be
increased. Set to zero for unlimited.

listeners(event)
7
Returns an array of listeners for the specified event.

emit(event, [arg1], [arg2], [...])

8 Execute each of the listeners in order with the supplied arguments. Returns true
if the event had listeners, false otherwise.

Class Methods
[Link]. Method & Description

1 listenerCount(emitter, event)
Returns the number of listeners for a given event.

36
 [Link]

Events
S. No. Events & Description

newListener

 event – String; the event name

1
 listener – Function; the event handler function

This event is emitted any time a listener is added. When this event is triggered,
the listener may not yet have been added to the array of listeners for the event.

removeListener

 event - String The event name

 listener - Function The event handler function

2

This event is emitted any time someone removes a listener. When this event is
triggered, the listener may not yet have been removed from the array of listeners
for the event.

Example
Create a js file named [Link] with the following [Link] code:

var events = require('events');

var eventEmitter = new [Link]();

// listener #1
var listner1 = function listner1() {
[Link]('listner1 executed.');
}
37
 [Link]

// listener #2
var listner2 = function listner2() {
[Link]('listner2 executed.');
}
// Bind the connection event with the listner1 function
[Link]('connection', listner1);
// Bind the connection event with the listner2 function
[Link]('connection', listner2);

var eventListeners =
require('events').[Link](eventEmitter,'connection');
[Link](eventListeners + " Listner(s) listening to connection event");

// Fire the connection event

[Link]('connection');

// Remove the binding of listner1 function

[Link]('connection', listner1);
[Link]("Listner1 will not listen now.");

// Fire the connection event

[Link]('connection');

eventListeners =
require('events').[Link](eventEmitter,'connection');
[Link](eventListeners + " Listner(s) listening to connection event");

[Link]("Program Ended.");

Now run the [Link] to see the result:

$ node [Link]

Verify the Output.

38
 [Link]

2 Listner(s) listening to connection event

listner1 executed.
listner2 executed.
Listner1 will not listen now.
listner2 executed.
1 Listner(s) listening to connection event
Program Ended.

39
 [Link]

End of ebook preview

If you liked what you saw…
Buy it from our store @ [Link]

40