Watching files for changes in Node.js - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of watching files for changes in Node.js?

Watching files for changes lets your program notice when a file is updated, added, or deleted. This helps automate tasks like reloading code or updating content without manual checks.

beginner

Which Node.js module is commonly used to watch files for changes?

The built-in fs module provides methods like fs.watch() and fs.watchFile() to watch files or directories for changes.

intermediate

What is the difference between fs.watch() and fs.watchFile()?

fs.watch() uses the operating system's native watching and is more efficient but less consistent across platforms. fs.watchFile() uses polling, checking the file at intervals, which is more consistent but can use more resources.

beginner

How do you stop watching a file using fs.watch()?

The fs.watch() method returns a watcher object. You call watcher.close() on this object to stop watching the file.

intermediate

Why is it important to handle errors when watching files?

Errors can happen if the file is deleted or permissions change. Handling errors prevents your program from crashing and lets you respond gracefully, like restarting the watcher or notifying the user.

Which Node.js method uses polling to watch files?

A fs.open()

B fs.watchFile()

C fs.readFile()

D fs.watch()

fs.watchFile() uses polling to check for file changes at intervals.

How do you stop watching a file with fs.watch()?

A Call watcher.close()

B Call fs.unwatch()

C Call fs.stop()

D Call watcher.stopWatching()

The watcher object returned by fs.watch() has a close() method to stop watching.

What event does fs.watch() emit when a file changes?

A "fileChanged"

B "update"

C "modify"

D "change"

fs.watch() emits a "change" event when the watched file or directory changes.

Which of these is NOT a benefit of watching files for changes?

A Manually checking files every minute

B Automatically reload code on changes

C Triggering tasks when files update

D Improving development workflow

Manually checking files is the opposite of watching files automatically.

What should you do if the watched file is deleted?

A Delete the watcher object without closing

B Ignore it and continue watching

C Handle the error and possibly restart watching

D Restart the whole Node.js process

Handling errors when files are deleted helps keep your program stable and responsive.

Explain how to watch a file for changes in Node.js using the fs module.

Think about the methods and how to start and stop watching.

Describe the differences between fs.watch() and fs.watchFile() and when you might use each.

Consider efficiency versus consistency.

Practice

1. What is the main purpose of using fs.watch in Node.js?

easy

A. To read the content of a file once

B. To write data to a file

C. To monitor changes in files or directories and react automatically

D. To delete a file from the system

Solution

1. Step 1: Understand the function of fs.watch

   fs.watch is designed to watch for changes in files or directories, triggering events when changes occur.

2. Step 2: Compare with other file operations

   Reading, writing, or deleting files are different operations handled by other functions like fs.readFile, fs.writeFile, or fs.unlink.

3. Final Answer:

   To monitor changes in files or directories and react automatically -> Option C

4. Quick Check:

   Watching files = react to changes [OK]

Hint: Remember: watch means observe changes, not read or write [OK]

Common Mistakes:

• Confusing watching with reading file content
• Thinking it deletes or modifies files
• Assuming it returns file data immediately

2. Which of the following is the correct syntax to watch a file named example.txt using fs.watch?

easy

A. fs.watch('example.txt', function(event) { console.log(event); });

B. fs.watch('example.txt', (eventType, filename) => { console.log(eventType); });

C. fs.watchFile('example.txt', (eventType, filename) => { console.log(filename); });

D. fs.watchFile('example.txt', function(filename) { console.log(filename); });

Solution

1. Step 1: Identify correct function and parameters

   fs.watch takes the filename and a callback with two parameters: eventType and filename.

2. Step 2: Check callback parameter correctness

   fs.watch('example.txt', (eventType, filename) => { console.log(eventType); }); correctly uses fs.watch with the right callback signature. The other options either use fs.watchFile or incorrect callback parameters.

3. Final Answer:

   fs.watch('example.txt', (eventType, filename) => { console.log(eventType); }); -> Option B

4. Quick Check:

   Correct syntax = fs.watch('example.txt', (eventType, filename) => { console.log(eventType); }); [OK]

Hint: Remember: fs.watch callback has (eventType, filename) parameters [OK]

Common Mistakes:

• Using fs.watchFile instead of fs.watch
• Using wrong callback parameters
• Omitting filename parameter in callback

3. What will be the output when running this code if test.txt is modified?

const fs = require('fs');
fs.watch('test.txt', (eventType, filename) => {
  if (filename) {
    console.log(`${filename} file changed with event: ${eventType}`);
  } else {
    console.log('filename not provided');
  }
});

medium

A. test.txt file changed with event: change

B. filename not provided

C. SyntaxError

D. No output

Solution

1. Step 1: Understand the callback behavior on file change

   When test.txt changes, fs.watch triggers the callback with eventType usually as 'change' and filename as 'test.txt'.

2. Step 2: Analyze the conditional output

   Since filename is provided, the code logs the filename and event type message.

3. Final Answer:

   test.txt file changed with event: change -> Option A

4. Quick Check:

   File changed event logs filename and event [OK]

Hint: If filename exists, output shows file and event type [OK]

Common Mistakes:

• Assuming filename is always undefined
• Expecting no output on file change
• Confusing eventType values

4. Identify the error in this code snippet that watches a file and logs changes:

const fs = require('fs');
fs.watch('log.txt', (event, file) => {
  console.log(file + ' changed');
});

medium

A. The file name string should be an absolute path

B. Missing error handling for fs.watch

C. fs.watch cannot watch files, only directories

D. Callback parameters are incorrect; should be (eventType, filename)

Solution

1. Step 1: Recall fs.watch callback signature

   fs.watch's callback takes two arguments: the first is the event type (conventionally eventType), the second is the filename (conventionally filename). The code uses (event, file), which mismatches the standard names.

2. Step 2: Identify the issue from options

   Callback parameters are incorrect; should be (eventType, filename) correctly states that the callback parameters are incorrect and should use (eventType, filename).

3. Final Answer:

   Callback parameters are incorrect; should be (eventType, filename) -> Option D

4. Quick Check:

   Correct callback params = (eventType, filename) [OK]

Hint: Use (eventType, filename) as callback parameters for clarity [OK]

Common Mistakes:

• Using non-standard callback parameter names
• Thinking fs.watch only works on directories
• Assuming relative path is invalid

5. You want to watch a directory logs and print the name of any new file created inside it. Which code snippet correctly achieves this?

hard

A. fs.watch('logs', (eventType, filename) => { if (eventType === 'rename' && filename) { console.log(`New file: ${filename}`); } });

B. fs.watch('logs', (eventType) => { if (eventType === 'change') { console.log('File changed'); } });

C. fs.watchFile('logs', (curr, prev) => { console.log('Directory changed'); });

D. fs.watch('logs', () => { console.log('Something changed'); });

Solution

1. Step 1: Understand event types for directory watching

   When watching a directory, the rename event indicates a file was added or removed.

2. Step 2: Check for filename and event type

   fs.watch('logs', (eventType, filename) => { if (eventType === 'rename' && filename) { console.log(`New file: ${filename}`); } }); checks for rename event and ensures filename is provided before logging the new file name, which is correct.

3. Step 3: Evaluate other options

   fs.watch('logs', (eventType) => { if (eventType === 'change') { console.log('File changed'); } }); only checks for change event and does not handle new files specifically. fs.watchFile('logs', (curr, prev) => { console.log('Directory changed'); }); uses fs.watchFile which is for files, not directories. fs.watch('logs', () => { console.log('Something changed'); }); logs on any change but does not specify new files.

4. Final Answer:

   fs.watch('logs', (eventType, filename) => { if (eventType === 'rename' && filename) { console.log(`New file: ${filename}`); } }); -> Option A

5. Quick Check:

   Use 'rename' event and check filename for new files [OK]

Hint: Use 'rename' event to detect new files in directory [OK]

Common Mistakes:

• Using 'change' event to detect new files
• Using fs.watchFile for directories
• Not checking if filename is provided