Sign in
Skip to solution
mediumFrontend

Explain what output() and outputFromObservable() are in modern Angular and how they differ from @Output().

978 views
01

Understand the problem

Discuss signals-based output mechanisms in modern Angular.

signalsoutput
02

Attempt it yourself

Sketch your approach before reading the solution — that's what interviews test.

Nudge consolestandby

Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.

03

Study the solution

output() declares a new signal-compatible output emitter that is clean and does not need @Output() or EventEmitter. outputFromObservable() bridges RxJS streams to output events, automatically cleaning up subscription on component teardown.

Solution ready — 2 min read

Classified // press E to declassify

04

Read the code

Declaring outputs with the output() API
import { Component, output } from '@angular/core';
import { interval } from 'rxjs';
import { outputFromObservable } from '@angular/core/rxjs-interop';

@Component({
  selector: 'app-timer-button',
  standalone: true,
  template: '<button (click)="triggerEvent()">Click Me</button>'
})
export class TimerButtonComponent {
  btnClick = output<string>();
  timerTick = outputFromObservable(interval(1000));

  triggerEvent() {
    this.btnClick.emit('Button clicked!');
  }
}
05

Join the discussion

Discussion (0)

Sign in to join the discussion.

No responses yet. Be the first to share what you think.

Transmission complete // awaiting log

KEEP THE
STREAK ALIVE.

Dossier 22 of 121 decoded in the Angular track. One more won't hurt.

Back to track