# Introduction
In stream processing, a `Sink` is a construct designed to consume elements generated by a `Stream`.
```text showLineNumbers=false
┌─── Type of the result produced by the Sink
| ┌─── Type of elements consumed by the Sink
| | ┌─── Type of any leftover elements
│ | | ┌─── Type of possible errors
│ │ | | ┌─── Type of required dependencies
▼ ▼ ▼ ▼ ▼
Sink<A, In, L, E, R>
```
Here's an overview of what a `Sink` does:
- It consumes a varying number of `In` elements, which may include zero, one, or multiple elements.
- It can encounter errors of type `E` during processing.
- It produces a result of type `A` once processing completes.
- It can also return a remainder of type `L`, representing any leftover elements.
To process a stream using a `Sink`, you can pass it directly to the `Stream.run` function:
**Example** (Using a Sink to Collect Stream Elements)
```ts twoslash
import { Stream, Sink, Effect } from "effect"
// ┌─── Stream<number, never, never>
// ▼
const stream = Stream.make(1, 2, 3)
// Create a sink to take the first 2 elements of the stream
//
// ┌─── Sink<Chunk<number>, number, number, never, never>
// ▼
const sink = Sink.take<number>(2)
// Run the stream through the sink to collect the elements
//
// ┌─── Effect<number, never, never>
// ▼
const sum = Stream.run(stream, sink)
Effect.runPromise(sum).then(console.log)
/*
Output:
{ _id: 'Chunk', values: [ 1, 2 ] }
*/
```
The type of `sink` is as follows:
```text showLineNumbers=false
┌─── result
| ┌─── consumed elements
| | ┌─── leftover elements
│ | | ┌─── no errors
│ │ | | ┌─── no dependencies
▼ ▼ ▼ ▼ ▼
Sink<Chunk<number>, number, number, never, never>
```
Here's the breakdown:
- `Chunk<number>`: The final result produced by the sink after processing elements (in this case, a [Chunk](/docs/data-types/chunk/) of numbers).
- `number` (first occurrence): The type of elements that the sink will consume from the stream.
- `number` (second occurrence): The type of leftover elements, if any, that are not consumed.
- `never` (first occurrence): Indicates that this sink does not produce any errors.
- `never` (second occurrence): Shows that no dependencies are required to operate this sink.
In stream processing, a Sink is a construct designed to consume elements generated by a Stream.
┌─── Type of the result produced by the Sink
| ┌─── Type of elements consumed by the Sink
| | ┌─── Type of any leftover elements
│ | | ┌─── Type of possible errors
│ │ | | ┌─── Type of required dependencies
▼ ▼ ▼ ▼ ▼
Sink<A, In, L, E, R>
Here’s an overview of what a Sink does:
It consumes a varying number of In elements, which may include zero, one, or multiple elements.
It can encounter errors of type E during processing.
It produces a result of type A once processing completes.
It can also return a remainder of type L, representing any leftover elements.
To process a stream using a Sink, you can pass it directly to the Stream.run function:
Executes an effect and returns the result as a Promise.
Details
This function runs an effect and converts its result into a Promise. If the
effect succeeds, the Promise will resolve with the successful result. If
the effect fails, the Promise will reject with an error, which includes the
failure details of the effect.
The optional options parameter allows you to pass an AbortSignal for
cancellation, enabling more fine-grained control over asynchronous tasks.
When to Use
Use this function when you need to execute an effect and work with its result
in a promise-based system, such as when integrating with third-party
libraries that expect Promise results.
Example (Running a Successful Effect as a Promise)
Attaches callbacks for the resolution and/or rejection of the Promise.
@param ― onfulfilled The callback to execute when the Promise is resolved.
@param ― onrejected The callback to execute when the Promise is rejected.
@returns ― A Promise for the completion of which ever callback is executed.
then(
var console:Console
The console module provides a simple debugging console that is similar to the
JavaScript console mechanism provided by web browsers.
The module exports two specific components:
A Console class with methods such as console.log(), console.error() and console.warn() that can be used to write to any Node.js stream.
A global console instance configured to write to process.stdout and
process.stderr. The global console can be used without importing the node:console module.
Warning: The global console object's methods are neither consistently
synchronous like the browser APIs they resemble, nor are they consistently
asynchronous like all other Node.js streams. See the note on process I/O for
more information.
Example using the global console:
console.log('hello world');
// Prints: hello world, to stdout
console.log('hello %s', 'world');
// Prints: hello world, to stdout
console.error(newError('Whoops, something bad happened'));
// Prints error message and stack trace to stderr:
// Error: Whoops, something bad happened
// at [eval]:5:15
// at Script.runInThisContext (node:vm:132:18)
// at Object.runInThisContext (node:vm:309:38)
// at node:internal/process/execution:77:19
// at [eval]-wrapper:6:22
// at evalScript (node:internal/process/execution:76:60)
// at node:internal/main/eval_string:23:3
constname='Will Robinson';
console.warn(`Danger ${name}! Danger!`);
// Prints: Danger Will Robinson! Danger!, to stderr
Example using the Console class:
constout=getStreamSomehow();
consterr=getStreamSomehow();
constmyConsole=new console.Console(out, err);
myConsole.log('hello world');
// Prints: hello world, to out
myConsole.log('hello %s', 'world');
// Prints: hello world, to out
myConsole.error(newError('Whoops, something bad happened'));
// Prints: [Error: Whoops, something bad happened], to err
Prints to stdout with newline. Multiple arguments can be passed, with the
first used as the primary message and all additional used as substitution
values similar to printf(3)
(the arguments are all passed to util.format()).