Socket.io integration with Express - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Socket.io library.

Express

const express = require('express');
const http = require('http');
const socketIo = require('[1]');

Drag options to blanks, or click blank then click option'

Asocket.io-client

Bexpress-socket

Csocket.io

Dsocket

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'socket.io-client' instead of 'socket.io'.

Using a wrong package name like 'socket'.

The correct package to import for Socket.io server is socket.io.

2fill in blank

medium

Complete the code to create an HTTP server from the Express app.

Express

const app = express();
const server = http.createServer([1]);

Drag options to blanks, or click blank then click option'

AsocketIo

Bhttp

Cexpress

Dapp

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the Socket.io instance instead of the Express app.

Passing the HTTP module itself.

The HTTP server is created from the Express app instance, so app is passed.

3fill in blank

hard

Fix the error in initializing Socket.io with the HTTP server.

Express

const io = socketIo([1]);

Drag options to blanks, or click blank then click option'

Aserver

Bapp

Chttp

Dexpress

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the Express app instead of the HTTP server.

Passing the HTTP module or express module.

Socket.io needs the HTTP server instance to bind to, so server is correct.

4fill in blank

hard

Fill both blanks to listen for a new client connection and log a message.

Express

io.on('[1]', (socket) => {
  console.log('A client [2]');
});

Drag options to blanks, or click blank then click option'

Aconnection

Bdisconnect

Cconnected

Dconnect

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'connect' or 'connected' as event name instead of 'connection'.

Using 'disconnect' event here.

The event to listen for new clients is 'connection' (A). The log message is A client connected, so {{BLANK_2}} is connected (C).

5fill in blank

hard

Fill all three blanks to emit a message to the client when connected.

Express

io.on('connection', ([1]) => {
  [2].[3]('welcome', 'Hello from server!');
});

Drag options to blanks, or click blank then click option'

Asocket

Bemit

Csend

Dconnection

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'send' instead of 'emit' to send events.

Using wrong parameter name instead of 'socket'.

The callback parameter is usually named socket. To send a message, call socket.emit. So the first and third blanks are 'socket', the second blank is 'emit'.

Practice

1. What is the main purpose of integrating Socket.io with an Express app?

easy

A. To handle database queries

B. To enable real-time, two-way communication between client and server

C. To serve static files faster

D. To improve server-side rendering speed

Solution

1. Step 1: Understand Socket.io's role

   Socket.io is designed to add real-time communication features to web apps.

2. Step 2: Compare with Express capabilities

   Express mainly handles HTTP requests but does not support real-time events natively.

3. Final Answer:

   To enable real-time, two-way communication between client and server -> Option B

4. Quick Check:

   Socket.io = real-time communication [OK]

Hint: Socket.io = real-time events, Express = HTTP server [OK]

Common Mistakes:

• Thinking Socket.io speeds up static file serving
• Confusing Socket.io with database handling
• Assuming Socket.io improves rendering speed

2. Which code snippet correctly initializes Socket.io with an Express app?

easy

A. const http = require('http'); const server = http.createServer(app); const io = require('socket.io')(server);

B. const io = require('socket.io')(app);

C. const io = require('socket.io').listen(app);

D. const io = require('socket.io').createServer(app);

Solution

1. Step 1: Recognize Express app needs HTTP server

   Socket.io requires a raw HTTP server, not just the Express app instance.

2. Step 2: Check correct Socket.io initialization

   Creating an HTTP server from Express app and passing it to Socket.io is the correct pattern.

3. Final Answer:

   const http = require('http'); const server = http.createServer(app); const io = require('socket.io')(server); -> Option A

4. Quick Check:

   Socket.io needs HTTP server, not Express app alone [OK]

Hint: Socket.io attaches to HTTP server, not Express app directly [OK]

Common Mistakes:

• Passing Express app directly to Socket.io
• Using deprecated listen or createServer methods
• Not creating an HTTP server from Express app

3. Given this code snippet, what will be logged when a client connects?

const http = require('http');
const express = require('express');
const app = express();
const server = http.createServer(app);
const { Server } = require('socket.io');
const io = new Server(server);
io.on('connection', (socket) => {
  console.log('User connected:', socket.id);
});
server.listen(3000);

medium

A. User connected: followed by a unique socket id

B. User connected: undefined

C. Error: socket.id is not defined

D. No output because connection event is not triggered

Solution

1. Step 1: Understand the connection event

   The 'connection' event fires when a client connects, passing a socket object.

2. Step 2: Check socket.id property

   Each socket has a unique id assigned automatically by Socket.io.

3. Final Answer:

   User connected: followed by a unique socket id -> Option A

4. Quick Check:

   socket.id exists on connection event [OK]

Hint: socket.id is unique and available on connection event [OK]

Common Mistakes:

• Assuming socket.id is undefined
• Expecting no output on connection
• Confusing socket object with request object

4. Identify the error in this Socket.io and Express integration code:

const express = require('express');
const app = express();
const io = require('socket.io')(app);
app.get('/', (req, res) => res.send('Hello'));
app.listen(3000);

medium

A. Missing event listener for 'connection' event

B. Express app cannot serve routes when Socket.io is used

C. app.listen should be called before Socket.io initialization

D. Socket.io should be attached to an HTTP server, not directly to app

Solution

1. Step 1: Check how Socket.io is initialized

   Socket.io requires an HTTP server instance, not the Express app directly.

2. Step 2: Identify correct server creation

   Must create HTTP server from Express app and pass it to Socket.io.

3. Final Answer:

   Socket.io should be attached to an HTTP server, not directly to app -> Option D

4. Quick Check:

   Socket.io needs HTTP server, not Express app [OK]

Hint: Attach Socket.io to HTTP server, not Express app [OK]

Common Mistakes:

• Passing Express app directly to Socket.io
• Ignoring need for HTTP server
• Thinking app.listen order matters here

5. You want to broadcast a message to all connected clients except the sender using Socket.io in Express. Which code snippet correctly does this inside the 'connection' event?

io.on('connection', (socket) => {
  // Broadcast 'hello' to others
  ???
});

hard

A. socket.emit('message', 'hello');

B. io.emit('message', 'hello');

C. socket.broadcast.emit('message', 'hello');

D. io.broadcast.emit('message', 'hello');

Solution

1. Step 1: Understand broadcasting in Socket.io

   To send to all except sender, use socket.broadcast.emit inside connection handler.

2. Step 2: Check each option's behavior

   io.emit sends to all including sender; socket.emit sends only to sender; io.broadcast.emit is invalid.

3. Final Answer:

   socket.broadcast.emit('message', 'hello'); -> Option C

4. Quick Check:

   Broadcast = socket.broadcast.emit [OK]

Hint: Use socket.broadcast.emit to exclude sender [OK]

Common Mistakes:

• Using io.emit which includes sender
• Using socket.emit which sends only to sender
• Trying io.broadcast.emit which does not exist