How Node.js differs from browser JavaScript in Node.js - Practice Exercises

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Global Objects in Node.js vs Browser

Which global object is available in Node.js but NOT in browser JavaScript?

A global

B navigator

C window

D document

💡 Hint

Think about the object that represents the global scope in Node.js.

In Node.js, the global object is called global. In browsers, it's window. Objects like document and navigator are browser-specific.

❓ component_behavior

intermediate

File System Access in Node.js vs Browser

What happens if you try to use Node.js's 'fs' module in browser JavaScript?

A It throws a ReferenceError because 'fs' is not defined

B It works normally and reads files from the user's computer

C It reads files but only from the browser cache

D It prompts the user to select files manually

💡 Hint

Consider what modules are available in browsers by default.

The 'fs' module is part of Node.js for file system operations. Browsers do not have access to this module, so trying to use it causes a ReferenceError.

📝 Syntax

advanced

Using ES Modules in Node.js vs Browser

Which statement about ES Modules (import/export) in Node.js and browsers is correct?

A Browsers do not support ES Modules natively

B Browsers require .mjs extension for ES Modules to work

C Node.js does not support ES Modules at all

D Node.js supports ES Modules natively only if files have .mjs extension or 'type':'module' in package.json

💡 Hint

Think about how Node.js handles module types compared to browsers.

Node.js supports ES Modules natively but requires either the .mjs file extension or setting 'type':'module' in package.json. Browsers support ES Modules natively without needing special extensions.

❓ state_output

advanced

Event Loop Behavior in Node.js vs Browser

What is a key difference in how the event loop handles timers in Node.js compared to browsers?

A Browsers queue timers in the microtask queue, Node.js does not

B Browsers execute timers immediately without delay, Node.js always delays

C Node.js uses separate phases for timers and I/O callbacks, browsers do not

D Node.js does not support setTimeout, browsers do

💡 Hint

Consider the phases of the Node.js event loop.

Node.js event loop has multiple phases including timers and I/O callbacks, which affects when timers run. Browsers have a simpler event loop model.

🔧 Debug

expert

Identifying Error When Using Browser API in Node.js

What error will occur if you run this Node.js code? const element = document.getElementById('app'); console.log(element);

A TypeError: getElementById is not a function

B ReferenceError: document is not defined

C SyntaxError: Unexpected identifier

D No error, logs null

💡 Hint

Think about what 'document' means in Node.js.

Node.js does not have a 'document' object because it does not run in a browser environment. Trying to access 'document' causes a ReferenceError.