Node's file system API is large enough that memorizing method names is a poor study strategy. I find it more useful to group the API by the decision a backend developer has to make. Here is a compact map you can use when learning or reviewing node:fs .
1. Pick the execution style
The module offers Promise, callback, and synchronous forms. Start by asking whether the operation is on a request path. A synchronous call blocks further JavaScript execution until it completes. For most application I/O, learn the asynchronous form first, then recognize its callback equivalent when reading older code.
Exercise: find readFile , writeFile , and stat in both the Promise and callback APIs. Explain how each reports an error.
2. Decide whether the whole file belongs in memory
Whole-file helpers are convenient for small configuration or text files. Streams are a different tool when you want to process data incrementally.…