Search documentation

Search by topic, API name, or import path.

GitHub ↗

variable / @typed/fx/Fx

fromEffect

Creates an Fx from an Effect.

If the Effect succeeds, the Fx emits the value and completes. If the Effect fails, the Fx fails with the same error.

Package version
2.0.0-beta.13
Category
Effect interop
Since
1.0.0

Follow one execution

The Effect runs once, emits its successful result, and returns. Failure instead forwards its Cause.

Fx timelinefromEffect(load)fromEffect
OperatorfromEffect(load)
Read this diagram

Follow each lane from left to right. Events stacked vertically share a tick; the green cursor marks the current time across every lane.

  • A value
    The text inside the pill is the emitted value.
  • Work starts
    The raised chevron starts an inner run (^ in the source).
  • The run returns
    The vertical bar ends this lane’s run.
  • A cause is delivered
    The exclamation mark belongs to this lane.
  • Work is interrupted
    The cross marks cancellation of this run.
  • Current time
    The line and diamond move together across all lanes.
  • Happening now
    A highlighted event is at the current tick.
  • Still ahead
    Muted, dashed values have not happened yet.
  • Time continues
    The lane’s arrow is not a return marker. An empty stretch can be quiet work that is still running.

Illustrated ticks start at 0. At 1×, one illustrated tick takes one second; captions specify real durations when timing matters. A cause or interruption belongs to its lane, and other work may continue. Scroll horizontally to inspect the rest of a long timeline.

Conversion is lazy. Each run executes the Effect once in the run’s fiber, forwards its success or full cause to the sink, and completes after the sink handler. The run’s interruption and scope own any acquisition performed by the Effect.

Source implementation · Learn the surrounding model

Compare all Fx timelines →

Import

import { fromEffect } from "@typed/fx/Fx";

Signatures

export declare const fromEffect: <A, E = never, R = never>(effect: Effect.Effect<A, E, R>) => Fx<A, E, R>;

Why

A single Effect result can enter push composition without losing its typed error or service requirements.

Ownership and lifetime

Conversion is lazy. Each run executes the Effect once in the run’s fiber, forwards its success or full cause to the sink, and completes after the sink handler. The run’s interruption and scope own any acquisition performed by the Effect.

Examples

import { Effect } from "effect"
import { collectAll, fromEffect } from "@typed/fx/Fx"

const source = fromEffect(Effect.succeed(42))
const program = collectAll(source)

Other public imports

These import paths expose the same declaration. Each page retains its own public name and signature.

Source