effect-resources-scope

Resource leaks occur when files, sockets, or external handles aren't properly closed. acquireRelease pairs acquisition and cleanup logic, guaranteeing release even on interruption. Wrap usage in a scoped block to ensure cleanup within an Effect-based runtime.

acquireRelease combines acquire and release as paired operations. scoped creates local resource lifecycles with guaranteed cleanup. Finalizers attach cleanup actions to resources. Use acquireRelease for explicit pairs, scoped for nested contexts, and finalizers for deferred cleanup within Effect workflows.

Yes. Wrap Promise APIs with typed errors and spans using acquireRelease. This converts untyped async operations into Effect's resource-safe model, applying cleanup guarantees and error handling to external handles and async workflows.

Scoped blocks and acquireRelease guarantee cleanup on interruption by registering finalizers with the Effect runtime. Resources are released regardless of success, error, or cancellation within the scoped context.

Use finalizers for deferred, guaranteed cleanup when you need certainty that a cleanup action runs at scope exit. Finalizers integrate with Effect's runtime supervision, making them safer than manual release in complex async workflows with multiple error paths.

Yes. Scoped resource management applies to servers, connection handles, and external services. Each scoped block binds resource acquisition to its exit, enabling safe pooling and multi-handle scenarios within an Effect runtime.