bun-file-io

Standardizing Bun file I/O operations involves using Bun.file for reading, writing, and scanning files to reduce codebase drift. It enforces consistent API patterns and provides basic guardrails for error handling across the project.

You can read and write files in Bun by adopting standardized Bun.file usage patterns. This approach provides clear guidance on preferred APIs for file operations, ensuring consistent editing, scanning, and deleting behaviors throughout your codebase.

For directory operations in Bun, you should use node:fs. While Bun APIs are enforced for reading, writing, and scanning files, the standardized pattern specifically recommends node:fs to handle directory-level operations for reliable project management.

Yes, the Bun file I/O pattern includes basic guardrails for error handling when deleting files. It streamlines file deletion tasks within the project workspace by providing clear guidance on preferred APIs to safely manage file removal.

You need to standardize file operations in your Bun codebase when file handling drift and errors become frequent. This pattern covers editing, reading, writing, scanning, and deleting files, ensuring all developers use consistent Bun API approaches.