Node.js File I/O: Whole-File Helpers, Streams, Random Access, and Durability

[giscus[bot]]

Node.js File I/O: Whole-File Helpers, Streams, Random Access, and Durability

How Node.js reads and writes files through whole-file helpers, streams, low-level read/write calls, append mode, and durable flushes.

https://www.thenodebook.com/file-system/reading-writing-files

[VesperQuartz]

is there a reason why you choose to use require instead of import for the examples given that we are in the year 2026?

[ishtms]

@VesperQuartz using require here was a personal choice, and not a statement like require is better than import. In 2026, require is still valid, stable and not outdated if you're thinking that way.

For new apps, import / export is generally the default. But that does not mean require is wrong, outdated in every context, or automatically less efficient.

Both of those (CJS and ESM) are stable. They have different rules, so it is not always a simple "replace require with import and everything works" situation.

For NodeBook, I used require because many readers are already familiar with it, and it keeps the focus on the concept being explained rather than on module-system setup. If someone is starting a brand-new app or library today, ESM is often the better default. But if they are maintaining an existing CommonJS project, using tools/packages that expect CommonJS, or they just want to build something for themselves require is still completely valid.

I would prefer import if I need a cleaner static structure, top-level await, and compatibility with browser/frontend tooling. I go into the CommonJS and ESM differences in more depth in this chapter - Modules in Node.js

[zessu]

idk how I feel about this decision. I think using import is a smarter decision long term. yes cjs is stable but almost no one builds a new project on it. I think ESM would just make this book seem "more modern" and more useful

[VesperQuartz]

var and let are also not outdated...

[ishtms]

@zessu I agree, you're not wrong though. Would be hard for me to update the content everywhere, but for now I can think about writing newer chapters that only rely on ESM syntax, starting with Volume 2. Thanks @VesperQuartz for raising this up.