signature: exhaustMap(project: function, resultSelector: function): Observable

Map to inner observable, ignore other values until that observable completes.

Why use exhaustMap?

Imagine you're at a coffee shop where each customer is allowed to place only one order at a time and must wait until that order is fully prepared before making another. If they try to order again while their coffee is still brewing, the barista simply ignores them. That's the essence of exhaustMap.

This operator is perfect for handling events that might be triggered multiple times in rapid succession but where only the initial trigger should be acted upon until it completes. A prime example would be ignoring clicks where a user might impatiently tap a 'Submit' button multiple times. Instead of sending multiple network requests, you'd ideally only want the first click to initiate the action and ignore subsequent clicks until the request is done.

Take note that exhaustMap will ignore source values while the previous inner observable is still active. This means that if the inner observable hasn't completed, any new values emitted from the source will be discarded without any mapping.

If you want to handle every single event, even if previous ones haven't completed, other operators like switchMap or mergeMap might be more appropriate. But when ensuring one task is exhausted before moving to the next, exhaustMap is your go-to choice.


Example 1: exhaustMap with interval

( Stackblitz | jsBin | jsFiddle )

// RxJS v6+
import { interval, merge, of } from 'rxjs';
import { delay, take, exhaustMap } from 'rxjs/operators';

const sourceInterval = interval(1000);
const delayedInterval = sourceInterval.pipe(delay(10), take(4));

const exhaustSub = merge(
  // delay 10ms, then start interval emitting 4 values
  // emit immediately
  .pipe(exhaustMap(_ => sourceInterval.pipe(take(5))))
   *  The first emitted value (of(true)) will be mapped
   *  to an interval observable emitting 1 value every
   *  second, completing after 5.
   *  Because the emissions from the delayed interval
   *  fall while this observable is still active they will be ignored.
   *  Contrast this with concatMap which would queue,
   *  switchMap which would switch to a new inner observable each emission,
   *  and mergeMap which would maintain a new subscription for each emitted value.
  // output: 0, 1, 2, 3, 4
  .subscribe(val => console.log(val));

Example 2: Another exhaustMap with interval

( Stackblitz | jsBin | jsFiddle )

// RxJS v6+
import { interval } from 'rxjs';
import { exhaustMap, tap, take } from 'rxjs/operators';

const firstInterval = interval(1000).pipe(take(10));
const secondInterval = interval(1000).pipe(take(2));

const exhaustSub = firstInterval
    exhaustMap(f => {
      console.log(`Emission Corrected of first interval: ${f}`);
      return secondInterval;
                When we subscribed to the first interval, it starts to emit a values (starting 0).
                This value is mapped to the second interval which then begins to emit (starting 0).  
                While the second interval is active, values from the first interval are ignored.
                We can see this when firstInterval emits number 3,6, and so on...

                  Emission of first interval: 0
                  Emission of first interval: 3
                  Emission of first interval: 6
                  Emission of first interval: 9
  .subscribe(s => console.log(s));

Outside Examples

exhaustMap for login effect in @ngrx example app

( Source )

  login$ = this.actions$.pipe(
    map((action: Login) => action.payload),
    exhaustMap((auth: Authenticate) =>
          map(user => new LoginSuccess({ user })),
          catchError(error => of(new LoginFailure(error)))

Additional Resources

📁 Source Code: https://github.com/ReactiveX/rxjs/blob/master/src/internal/operators/exhaustMap.ts

Last updated