effect-platform-abstraction

Cross-platform TypeScript code requires replacing direct Node.js and Bun APIs with Effect platform abstractions for filesystem and process spawning. Using services like FileSystem, HttpClient, and Terminal ensures your application runs unchanged on both runtimes while keeping behavior consistent and testable.

The best way to handle file I/O without the fs module is using Effect's FileSystem service. This platform abstraction replaces direct fs or fs/promises calls, providing type-safe errors and resource safety through Effect's service and Scope-based design across Node.js and Bun environments.

Yes, you can use Effect's HttpClient service instead of fetch or axios for HTTP requests. This platform abstraction provides portable, type-safe network access that runs consistently across Node.js and Bun, avoiding environment-specific bugs caused by direct global API usage.

To spawn child processes portably across Node.js and Bun, use Effect's ChildProcessSpawner service instead of direct child_process imports. This abstraction ensures consistent process spawning behavior and integrates with Effect's resource management for safe cleanup.

Using the Node.js path module causes bugs because it couples your code to a specific runtime environment. Replacing it with Effect's Path service provides safe, correct path handling that remains consistent across Node.js and Bun, avoiding manual string concatenation errors.

Yes, you need appropriate runtime and platform layers like NodeServices or BunServices to use Effect platform abstractions for terminal I/O. These layers provide the environment-specific implementations that back Effect's Terminal service, ensuring consistent behavior across runtimes.