effect-filesystem

Cross-platform file I/O with Effect uses a single FileSystem abstraction for consistent reads, writes, and directory management across Node.js, Bun, and browsers. You yield the FileSystem service, use PlatformError-safe error handling, and rely on platform layers at the entry point.

Yes, streaming large files in Effect avoids memory overload by streaming inputs and writing via sinks. This approach allows you to process large data streams safely across Node.js, Bun, and browser environments.

Yes, the Effect FileSystem abstraction supports robust metadata and permission operations. You can stat files, check access or existence, resolve real paths, and perform chmod, chown, and utimes operations.

The best way to handle platform-specific file errors in Effect is using PlatformError-safe error handling. This mechanism wraps platform-specific failures into a consistent error type across Node.js, Bun, and browser scenarios.

You manage temporary or scoped file resources in Effect by yielding the FileSystem service within a scoped workflow. This ensures temporary files and directories are safely acquired and automatically cleaned up.

Yes, you need platform layers at your application entry point to provide the concrete FileSystem implementation. Once provided, you can yield the FileSystem service to read file strings or binary data consistently.