@bleedingdev/modern-js-utils 3.9.0-ultramodern.9 → 3.9.3-ultramodern.1

package/dist/compiled/inquirer/rxjs/internal/observable/combineLatest.d.ts

@@ -1,33 +0,0 @@
-import { Observable } from '../Observable';
-import { ObservableInput, SchedulerLike, ObservedValueOf, ObservableInputTuple } from '../types';
-import { Subscriber } from '../Subscriber';
-import { AnyCatcher } from '../AnyCatcher';
-/**
- * You have passed `any` here, we can't figure out if it is
- * an array or an object, so you're getting `unknown`. Use better types.
- * @param arg Something typed as `any`
- */
-export declare function combineLatest<T extends AnyCatcher>(arg: T): Observable<unknown>;
-export declare function combineLatest(sources: []): Observable<never>;
-export declare function combineLatest<A extends readonly unknown[]>(sources: readonly [...ObservableInputTuple<A>]): Observable<A>;
-/** @deprecated The `scheduler` parameter will be removed in v8. Use `scheduled` and `combineLatestAll`. Details: https://rxjs.dev/deprecations/scheduler-argument */
-export declare function combineLatest<A extends readonly unknown[], R>(sources: readonly [...ObservableInputTuple<A>], resultSelector: (...values: A) => R, scheduler: SchedulerLike): Observable<R>;
-export declare function combineLatest<A extends readonly unknown[], R>(sources: readonly [...ObservableInputTuple<A>], resultSelector: (...values: A) => R): Observable<R>;
-/** @deprecated The `scheduler` parameter will be removed in v8. Use `scheduled` and `combineLatestAll`. Details: https://rxjs.dev/deprecations/scheduler-argument */
-export declare function combineLatest<A extends readonly unknown[]>(sources: readonly [...ObservableInputTuple<A>], scheduler: SchedulerLike): Observable<A>;
-/** @deprecated Pass an array of sources instead. The rest-parameters signature will be removed in v8. Details: https://rxjs.dev/deprecations/array-argument */
-export declare function combineLatest<A extends readonly unknown[]>(...sources: [...ObservableInputTuple<A>]): Observable<A>;
-/** @deprecated The `scheduler` parameter will be removed in v8. Use `scheduled` and `combineLatestAll`. Details: https://rxjs.dev/deprecations/scheduler-argument */
-export declare function combineLatest<A extends readonly unknown[], R>(...sourcesAndResultSelectorAndScheduler: [...ObservableInputTuple<A>, (...values: A) => R, SchedulerLike]): Observable<R>;
-/** @deprecated Pass an array of sources instead. The rest-parameters signature will be removed in v8. Details: https://rxjs.dev/deprecations/array-argument */
-export declare function combineLatest<A extends readonly unknown[], R>(...sourcesAndResultSelector: [...ObservableInputTuple<A>, (...values: A) => R]): Observable<R>;
-/** @deprecated The `scheduler` parameter will be removed in v8. Use `scheduled` and `combineLatestAll`. Details: https://rxjs.dev/deprecations/scheduler-argument */
-export declare function combineLatest<A extends readonly unknown[]>(...sourcesAndScheduler: [...ObservableInputTuple<A>, SchedulerLike]): Observable<A>;
-export declare function combineLatest(sourcesObject: {
-    [K in any]: never;
-}): Observable<never>;
-export declare function combineLatest<T extends Record<string, ObservableInput<any>>>(sourcesObject: T): Observable<{
-    [K in keyof T]: ObservedValueOf<T[K]>;
-}>;
-export declare function combineLatestInit(observables: ObservableInput<any>[], scheduler?: SchedulerLike, valueTransform?: (values: any[]) => any): (subscriber: Subscriber<any>) => void;
-//# sourceMappingURL=combineLatest.d.ts.map

package/dist/compiled/inquirer/rxjs/internal/observable/concat.d.ts

@@ -1,5 +0,0 @@
-import { Observable } from '../Observable';
-import { ObservableInputTuple, SchedulerLike } from '../types';
-export declare function concat<T extends readonly unknown[]>(...inputs: [...ObservableInputTuple<T>]): Observable<T[number]>;
-export declare function concat<T extends readonly unknown[]>(...inputsAndScheduler: [...ObservableInputTuple<T>, SchedulerLike]): Observable<T[number]>;
-//# sourceMappingURL=concat.d.ts.map

package/dist/compiled/inquirer/rxjs/internal/observable/connectable.d.ts

@@ -1,27 +0,0 @@
-import { Connectable, ObservableInput, SubjectLike } from '../types';
-export interface ConnectableConfig<T> {
-    /**
-     * A factory function used to create the Subject through which the source
-     * is multicast. By default this creates a {@link Subject}.
-     */
-    connector: () => SubjectLike<T>;
-    /**
-     * If true, the resulting observable will reset internal state upon disconnection
-     * and return to a "cold" state. This allows the resulting observable to be
-     * reconnected.
-     * If false, upon disconnection, the connecting subject will remain the
-     * connecting subject, meaning the resulting observable will not go "cold" again,
-     * and subsequent repeats or resubscriptions will resubscribe to that same subject.
-     */
-    resetOnDisconnect?: boolean;
-}
-/**
- * Creates an observable that multicasts once `connect()` is called on it.
- *
- * @param source The observable source to make connectable.
- * @param config The configuration object for `connectable`.
- * @returns A "connectable" observable, that has a `connect()` method, that you must call to
- * connect the source to all consumers through the subject provided as the connector.
- */
-export declare function connectable<T>(source: ObservableInput<T>, config?: ConnectableConfig<T>): Connectable<T>;
-//# sourceMappingURL=connectable.d.ts.map

package/dist/compiled/inquirer/rxjs/internal/observable/defer.d.ts

@@ -1,51 +0,0 @@
-import { Observable } from '../Observable';
-import { ObservedValueOf, ObservableInput } from '../types';
-/**
- * Creates an Observable that, on subscribe, calls an Observable factory to
- * make an Observable for each new Observer.
- *
- * <span class="informal">Creates the Observable lazily, that is, only when it
- * is subscribed.
- * </span>
- *
- * ![](defer.png)
- *
- * `defer` allows you to create an Observable only when the Observer
- * subscribes. It waits until an Observer subscribes to it, calls the given
- * factory function to get an Observable -- where a factory function typically
- * generates a new Observable -- and subscribes the Observer to this Observable.
- * In case the factory function returns a falsy value, then EMPTY is used as
- * Observable instead. Last but not least, an exception during the factory
- * function call is transferred to the Observer by calling `error`.
- *
- * ## Example
- *
- * Subscribe to either an Observable of clicks or an Observable of interval, at random
- *
- * ```ts
- * import { defer, fromEvent, interval } from '../..';
- *
- * const clicksOrInterval = defer(() => {
- *   return Math.random() > 0.5
- *     ? fromEvent(document, 'click')
- *     : interval(1000);
- * });
- * clicksOrInterval.subscribe(x => console.log(x));
- *
- * // Results in the following behavior:
- * // If the result of Math.random() is greater than 0.5 it will listen
- * // for clicks anywhere on the "document"; when document is clicked it
- * // will log a MouseEvent object to the console. If the result is less
- * // than 0.5 it will emit ascending numbers, one every second(1000ms).
- * ```
- *
- * @see {@link Observable}
- *
- * @param observableFactory The Observable factory function to invoke for each
- * Observer that subscribes to the output Observable. May also return any
- * `ObservableInput`, which will be converted on the fly to an Observable.
- * @return An Observable whose Observers' subscriptions trigger an invocation of the
- * given Observable factory function.
- */
-export declare function defer<R extends ObservableInput<any>>(observableFactory: () => R): Observable<ObservedValueOf<R>>;
-//# sourceMappingURL=defer.d.ts.map

package/dist/compiled/inquirer/rxjs/internal/observable/dom/WebSocketSubject.d.ts

@@ -1,173 +0,0 @@
-import { AnonymousSubject } from '../../Subject';
-import { Observable } from '../../Observable';
-import { Operator } from '../../Operator';
-import { Observer, NextObserver } from '../../types';
-/**
- * WebSocketSubjectConfig is a plain Object that allows us to make our
- * webSocket configurable.
- *
- * <span class="informal">Provides flexibility to {@link webSocket}</span>
- *
- * It defines a set of properties to provide custom behavior in specific
- * moments of the socket's lifecycle. When the connection opens we can
- * use `openObserver`, when the connection is closed `closeObserver`, if we
- * are interested in listening for data coming from server: `deserializer`,
- * which allows us to customize the deserialization strategy of data before passing it
- * to the socket client. By default, `deserializer` is going to apply `JSON.parse` to each message coming
- * from the Server.
- *
- * ## Examples
- *
- * **deserializer**, the default for this property is `JSON.parse` but since there are just two options
- * for incoming data, either be text or binary data. We can apply a custom deserialization strategy
- * or just simply skip the default behaviour.
- *
- * ```ts
- * import { webSocket } from 'rxjs/webSocket';
- *
- * const wsSubject = webSocket({
- *   url: 'ws://localhost:8081',
- *   //Apply any transformation of your choice.
- *   deserializer: ({ data }) => data
- * });
- *
- * wsSubject.subscribe(console.log);
- *
- * // Let's suppose we have this on the Server: ws.send('This is a msg from the server')
- * //output
- * //
- * // This is a msg from the server
- * ```
- *
- * **serializer** allows us to apply custom serialization strategy but for the outgoing messages.
- *
- * ```ts
- * import { webSocket } from 'rxjs/webSocket';
- *
- * const wsSubject = webSocket({
- *   url: 'ws://localhost:8081',
- *   // Apply any transformation of your choice.
- *   serializer: msg => JSON.stringify({ channel: 'webDevelopment', msg: msg })
- * });
- *
- * wsSubject.subscribe(() => subject.next('msg to the server'));
- *
- * // Let's suppose we have this on the Server:
- * //   ws.on('message', msg => console.log);
- * //   ws.send('This is a msg from the server');
- * // output at server side:
- * //
- * // {"channel":"webDevelopment","msg":"msg to the server"}
- * ```
- *
- * **closeObserver** allows us to set a custom error when an error raises up.
- *
- * ```ts
- * import { webSocket } from 'rxjs/webSocket';
- *
- * const wsSubject = webSocket({
- *   url: 'ws://localhost:8081',
- *   closeObserver: {
- *     next() {
- *       const customError = { code: 6666, reason: 'Custom evil reason' }
- *       console.log(`code: ${ customError.code }, reason: ${ customError.reason }`);
- *     }
- *   }
- * });
- *
- * // output
- * // code: 6666, reason: Custom evil reason
- * ```
- *
- * **openObserver**, Let's say we need to make some kind of init task before sending/receiving msgs to the
- * webSocket or sending notification that the connection was successful, this is when
- * openObserver is useful for.
- *
- * ```ts
- * import { webSocket } from 'rxjs/webSocket';
- *
- * const wsSubject = webSocket({
- *   url: 'ws://localhost:8081',
- *   openObserver: {
- *     next: () => {
- *       console.log('Connection ok');
- *     }
- *   }
- * });
- *
- * // output
- * // Connection ok
- * ```
- */
-export interface WebSocketSubjectConfig<T> {
-    /** The url of the socket server to connect to */
-    url: string;
-    /** The protocol to use to connect */
-    protocol?: string | Array<string>;
-    /** @deprecated Will be removed in v8. Use {@link deserializer} instead. */
-    resultSelector?: (e: MessageEvent) => T;
-    /**
-     * A serializer used to create messages from passed values before the
-     * messages are sent to the server. Defaults to JSON.stringify.
-     */
-    serializer?: (value: T) => WebSocketMessage;
-    /**
-     * A deserializer used for messages arriving on the socket from the
-     * server. Defaults to JSON.parse.
-     */
-    deserializer?: (e: MessageEvent) => T;
-    /**
-     * An Observer that watches when open events occur on the underlying web socket.
-     */
-    openObserver?: NextObserver<Event>;
-    /**
-     * An Observer that watches when close events occur on the underlying web socket
-     */
-    closeObserver?: NextObserver<CloseEvent>;
-    /**
-     * An Observer that watches when a close is about to occur due to
-     * unsubscription.
-     */
-    closingObserver?: NextObserver<void>;
-    /**
-     * A WebSocket constructor to use. This is useful for situations like using a
-     * WebSocket impl in Node (WebSocket is a DOM API), or for mocking a WebSocket
-     * for testing purposes
-     */
-    WebSocketCtor?: {
-        new (url: string, protocols?: string | string[]): WebSocket;
-    };
-    /** Sets the `binaryType` property of the underlying WebSocket. */
-    binaryType?: 'blob' | 'arraybuffer';
-}
-export declare type WebSocketMessage = string | ArrayBuffer | Blob | ArrayBufferView;
-export declare class WebSocketSubject<T> extends AnonymousSubject<T> {
-    private _config;
-    private _socket;
-    constructor(urlConfigOrSource: string | WebSocketSubjectConfig<T> | Observable<T>, destination?: Observer<T>);
-    /** @deprecated Internal implementation detail, do not use directly. Will be made internal in v8. */
-    lift<R>(operator: Operator<T, R>): WebSocketSubject<R>;
-    private _resetState;
-    /**
-     * Creates an {@link Observable}, that when subscribed to, sends a message,
-     * defined by the `subMsg` function, to the server over the socket to begin a
-     * subscription to data over that socket. Once data arrives, the
-     * `messageFilter` argument will be used to select the appropriate data for
-     * the resulting Observable. When finalization occurs, either due to
-     * unsubscription, completion, or error, a message defined by the `unsubMsg`
-     * argument will be sent to the server over the WebSocketSubject.
-     *
-     * @param subMsg A function to generate the subscription message to be sent to
-     * the server. This will still be processed by the serializer in the
-     * WebSocketSubject's config. (Which defaults to JSON serialization)
-     * @param unsubMsg A function to generate the unsubscription message to be
-     * sent to the server at finalization. This will still be processed by the
-     * serializer in the WebSocketSubject's config.
-     * @param messageFilter A predicate for selecting the appropriate messages
-     * from the server for the output stream.
-     */
-    multiplex(subMsg: () => any, unsubMsg: () => any, messageFilter: (value: T) => boolean): Observable<T>;
-    private _connectSocket;
-    unsubscribe(): void;
-}
-//# sourceMappingURL=WebSocketSubject.d.ts.map

package/dist/compiled/inquirer/rxjs/internal/observable/dom/animationFrames.d.ts

@@ -1,76 +0,0 @@
-import { Observable } from '../../Observable';
-import { TimestampProvider } from '../../types';
-/**
- * An observable of animation frames
- *
- * Emits the amount of time elapsed since subscription and the timestamp on each animation frame.
- * Defaults to milliseconds provided to the requestAnimationFrame's callback. Does not end on its own.
- *
- * Every subscription will start a separate animation loop. Since animation frames are always scheduled
- * by the browser to occur directly before a repaint, scheduling more than one animation frame synchronously
- * should not be much different or have more overhead than looping over an array of events during
- * a single animation frame. However, if for some reason the developer would like to ensure the
- * execution of animation-related handlers are all executed during the same task by the engine,
- * the `share` operator can be used.
- *
- * This is useful for setting up animations with RxJS.
- *
- * ## Examples
- *
- * Tweening a div to move it on the screen
- *
- * ```ts
- * import { animationFrames, map, takeWhile, endWith } from '../../..';
- *
- * function tween(start: number, end: number, duration: number) {
- *   const diff = end - start;
- *   return animationFrames().pipe(
- *     // Figure out what percentage of time has passed
- *     map(({ elapsed }) => elapsed / duration),
- *     // Take the vector while less than 100%
- *     takeWhile(v => v < 1),
- *     // Finish with 100%
- *     endWith(1),
- *     // Calculate the distance traveled between start and end
- *     map(v => v * diff + start)
- *   );
- * }
- *
- * // Setup a div for us to move around
- * const div = document.createElement('div');
- * document.body.appendChild(div);
- * div.style.position = 'absolute';
- * div.style.width = '40px';
- * div.style.height = '40px';
- * div.style.backgroundColor = 'lime';
- * div.style.transform = 'translate3d(10px, 0, 0)';
- *
- * tween(10, 200, 4000).subscribe(x => {
- *   div.style.transform = `translate3d(${ x }px, 0, 0)`;
- * });
- * ```
- *
- * Providing a custom timestamp provider
- *
- * ```ts
- * import { animationFrames, TimestampProvider } from '../../..';
- *
- * // A custom timestamp provider
- * let now = 0;
- * const customTSProvider: TimestampProvider = {
- *   now() { return now++; }
- * };
- *
- * const source$ = animationFrames(customTSProvider);
- *
- * // Log increasing numbers 0...1...2... on every animation frame.
- * source$.subscribe(({ elapsed }) => console.log(elapsed));
- * ```
- *
- * @param timestampProvider An object with a `now` method that provides a numeric timestamp
- */
-export declare function animationFrames(timestampProvider?: TimestampProvider): Observable<{
-    timestamp: number;
-    elapsed: number;
-}>;
-//# sourceMappingURL=animationFrames.d.ts.map

package/dist/compiled/inquirer/rxjs/internal/observable/dom/fetch.d.ts

@@ -1,7 +0,0 @@
-import { Observable } from '../../Observable';
-import { ObservableInput } from '../../types';
-export declare function fromFetch<T>(input: string | Request, init: RequestInit & {
-    selector: (response: Response) => ObservableInput<T>;
-}): Observable<T>;
-export declare function fromFetch(input: string | Request, init?: RequestInit): Observable<Response>;
-//# sourceMappingURL=fetch.d.ts.map

package/dist/compiled/inquirer/rxjs/internal/observable/dom/webSocket.d.ts

@@ -1,159 +0,0 @@
-import { WebSocketSubject, WebSocketSubjectConfig } from './WebSocketSubject';
-/**
- * Wrapper around the w3c-compatible WebSocket object provided by the browser.
- *
- * <span class="informal">{@link Subject} that communicates with a server via WebSocket</span>
- *
- * `webSocket` is a factory function that produces a `WebSocketSubject`,
- * which can be used to make WebSocket connection with an arbitrary endpoint.
- * `webSocket` accepts as an argument either a string with url of WebSocket endpoint, or an
- * {@link WebSocketSubjectConfig} object for providing additional configuration, as
- * well as Observers for tracking lifecycle of WebSocket connection.
- *
- * When `WebSocketSubject` is subscribed, it attempts to make a socket connection,
- * unless there is one made already. This means that many subscribers will always listen
- * on the same socket, thus saving resources. If however, two instances are made of `WebSocketSubject`,
- * even if these two were provided with the same url, they will attempt to make separate
- * connections. When consumer of a `WebSocketSubject` unsubscribes, socket connection is closed,
- * only if there are no more subscribers still listening. If after some time a consumer starts
- * subscribing again, connection is reestablished.
- *
- * Once connection is made, whenever a new message comes from the server, `WebSocketSubject` will emit that
- * message as a value in the stream. By default, a message from the socket is parsed via `JSON.parse`. If you
- * want to customize how deserialization is handled (if at all), you can provide custom `resultSelector`
- * function in {@link WebSocketSubject}. When connection closes, stream will complete, provided it happened without
- * any errors. If at any point (starting, maintaining or closing a connection) there is an error,
- * stream will also error with whatever WebSocket API has thrown.
- *
- * By virtue of being a {@link Subject}, `WebSocketSubject` allows for receiving and sending messages from the server. In order
- * to communicate with a connected endpoint, use `next`, `error` and `complete` methods. `next` sends a value to the server, so bear in mind
- * that this value will not be serialized beforehand. Because of This, `JSON.stringify` will have to be called on a value by hand,
- * before calling `next` with a result. Note also that if at the moment of nexting value
- * there is no socket connection (for example no one is subscribing), those values will be buffered, and sent when connection
- * is finally established. `complete` method closes socket connection. `error` does the same,
- * as well as notifying the server that something went wrong via status code and string with details of what happened.
- * Since status code is required in WebSocket API, `WebSocketSubject` does not allow, like regular `Subject`,
- * arbitrary values being passed to the `error` method. It needs to be called with an object that has `code`
- * property with status code number and optional `reason` property with string describing details
- * of an error.
- *
- * Calling `next` does not affect subscribers of `WebSocketSubject` - they have no
- * information that something was sent to the server (unless of course the server
- * responds somehow to a message). On the other hand, since calling `complete` triggers
- * an attempt to close socket connection. If that connection is closed without any errors, stream will
- * complete, thus notifying all subscribers. And since calling `error` closes
- * socket connection as well, just with a different status code for the server, if closing itself proceeds
- * without errors, subscribed Observable will not error, as one might expect, but complete as usual. In both cases
- * (calling `complete` or `error`), if process of closing socket connection results in some errors, *then* stream
- * will error.
- *
- * **Multiplexing**
- *
- * `WebSocketSubject` has an additional operator, not found in other Subjects. It is called `multiplex` and it is
- * used to simulate opening several socket connections, while in reality maintaining only one.
- * For example, an application has both chat panel and real-time notifications about sport news. Since these are two distinct functions,
- * it would make sense to have two separate connections for each. Perhaps there could even be two separate services with WebSocket
- * endpoints, running on separate machines with only GUI combining them together. Having a socket connection
- * for each functionality could become too resource expensive. It is a common pattern to have single
- * WebSocket endpoint that acts as a gateway for the other services (in this case chat and sport news services).
- * Even though there is a single connection in a client app, having the ability to manipulate streams as if it
- * were two separate sockets is desirable. This eliminates manually registering and unregistering in a gateway for
- * given service and filter out messages of interest. This is exactly what `multiplex` method is for.
- *
- * Method accepts three parameters. First two are functions returning subscription and unsubscription messages
- * respectively. These are messages that will be sent to the server, whenever consumer of resulting Observable
- * subscribes and unsubscribes. Server can use them to verify that some kind of messages should start or stop
- * being forwarded to the client. In case of the above example application, after getting subscription message with proper identifier,
- * gateway server can decide that it should connect to real sport news service and start forwarding messages from it.
- * Note that both messages will be sent as returned by the functions, they are by default serialized using JSON.stringify, just
- * as messages pushed via `next`. Also bear in mind that these messages will be sent on *every* subscription and
- * unsubscription. This is potentially dangerous, because one consumer of an Observable may unsubscribe and the server
- * might stop sending messages, since it got unsubscription message. This needs to be handled
- * on the server or using {@link publish} on a Observable returned from 'multiplex'.
- *
- * Last argument to `multiplex` is a `messageFilter` function which should return a boolean. It is used to filter out messages
- * sent by the server to only those that belong to simulated WebSocket stream. For example, server might mark these
- * messages with some kind of string identifier on a message object and `messageFilter` would return `true`
- * if there is such identifier on an object emitted by the socket. Messages which returns `false` in `messageFilter` are simply skipped,
- * and are not passed down the stream.
- *
- * Return value of `multiplex` is an Observable with messages incoming from emulated socket connection. Note that this
- * is not a `WebSocketSubject`, so calling `next` or `multiplex` again will fail. For pushing values to the
- * server, use root `WebSocketSubject`.
- *
- * ## Examples
- *
- * Listening for messages from the server
- *
- * ```ts
- * import { webSocket } from 'rxjs/webSocket';
- *
- * const subject = webSocket('ws://localhost:8081');
- *
- * subject.subscribe({
- *   next: msg => console.log('message received: ' + msg), // Called whenever there is a message from the server.
- *   error: err => console.log(err), // Called if at any point WebSocket API signals some kind of error.
- *   complete: () => console.log('complete') // Called when connection is closed (for whatever reason).
- *  });
- * ```
- *
- * Pushing messages to the server
- *
- * ```ts
- * import { webSocket } from 'rxjs/webSocket';
- *
- * const subject = webSocket('ws://localhost:8081');
- *
- * subject.subscribe();
- * // Note that at least one consumer has to subscribe to the created subject - otherwise "nexted" values will be just buffered and not sent,
- * // since no connection was established!
- *
- * subject.next({ message: 'some message' });
- * // This will send a message to the server once a connection is made. Remember value is serialized with JSON.stringify by default!
- *
- * subject.complete(); // Closes the connection.
- *
- * subject.error({ code: 4000, reason: 'I think our app just broke!' });
- * // Also closes the connection, but let's the server know that this closing is caused by some error.
- * ```
- *
- * Multiplexing WebSocket
- *
- * ```ts
- * import { webSocket } from 'rxjs/webSocket';
- *
- * const subject = webSocket('ws://localhost:8081');
- *
- * const observableA = subject.multiplex(
- *   () => ({ subscribe: 'A' }), // When server gets this message, it will start sending messages for 'A'...
- *   () => ({ unsubscribe: 'A' }), // ...and when gets this one, it will stop.
- *   message => message.type === 'A' // If the function returns `true` message is passed down the stream. Skipped if the function returns false.
- * );
- *
- * const observableB = subject.multiplex( // And the same goes for 'B'.
- *   () => ({ subscribe: 'B' }),
- *   () => ({ unsubscribe: 'B' }),
- *   message => message.type === 'B'
- * );
- *
- * const subA = observableA.subscribe(messageForA => console.log(messageForA));
- * // At this moment WebSocket connection is established. Server gets '{"subscribe": "A"}' message and starts sending messages for 'A',
- * // which we log here.
- *
- * const subB = observableB.subscribe(messageForB => console.log(messageForB));
- * // Since we already have a connection, we just send '{"subscribe": "B"}' message to the server. It starts sending messages for 'B',
- * // which we log here.
- *
- * subB.unsubscribe();
- * // Message '{"unsubscribe": "B"}' is sent to the server, which stops sending 'B' messages.
- *
- * subA.unsubscribe();
- * // Message '{"unsubscribe": "A"}' makes the server stop sending messages for 'A'. Since there is no more subscribers to root Subject,
- * // socket connection closes.
- * ```
- *
- * @param urlConfigOrSource The WebSocket endpoint as an url or an object with configuration and additional Observers.
- * @return Subject which allows to both send and receive messages via WebSocket connection.
- */
-export declare function webSocket<T>(urlConfigOrSource: string | WebSocketSubjectConfig<T>): WebSocketSubject<T>;
-//# sourceMappingURL=webSocket.d.ts.map

package/dist/compiled/inquirer/rxjs/internal/observable/empty.d.ts

@@ -1,72 +0,0 @@
-import { Observable } from '../Observable';
-import { SchedulerLike } from '../types';
-/**
- * A simple Observable that emits no items to the Observer and immediately
- * emits a complete notification.
- *
- * <span class="informal">Just emits 'complete', and nothing else.</span>
- *
- * ![](empty.png)
- *
- * A simple Observable that only emits the complete notification. It can be used
- * for composing with other Observables, such as in a {@link mergeMap}.
- *
- * ## Examples
- *
- * Log complete notification
- *
- * ```ts
- * import { EMPTY } from '../..';
- *
- * EMPTY.subscribe({
- *   next: () => console.log('Next'),
- *   complete: () => console.log('Complete!')
- * });
- *
- * // Outputs
- * // Complete!
- * ```
- *
- * Emit the number 7, then complete
- *
- * ```ts
- * import { EMPTY, startWith } from '../..';
- *
- * const result = EMPTY.pipe(startWith(7));
- * result.subscribe(x => console.log(x));
- *
- * // Outputs
- * // 7
- * ```
- *
- * Map and flatten only odd numbers to the sequence `'a'`, `'b'`, `'c'`
- *
- * ```ts
- * import { interval, mergeMap, of, EMPTY } from '../..';
- *
- * const interval$ = interval(1000);
- * const result = interval$.pipe(
- *   mergeMap(x => x % 2 === 1 ? of('a', 'b', 'c') : EMPTY),
- * );
- * result.subscribe(x => console.log(x));
- *
- * // Results in the following to the console:
- * // x is equal to the count on the interval, e.g. (0, 1, 2, 3, ...)
- * // x will occur every 1000ms
- * // if x % 2 is equal to 1, print a, b, c (each on its own)
- * // if x % 2 is not equal to 1, nothing will be output
- * ```
- *
- * @see {@link Observable}
- * @see {@link NEVER}
- * @see {@link of}
- * @see {@link throwError}
- */
-export declare const EMPTY: Observable<never>;
-/**
- * @param scheduler A {@link SchedulerLike} to use for scheduling
- * the emission of the complete notification.
- * @deprecated Replaced with the {@link EMPTY} constant or {@link scheduled} (e.g. `scheduled([], scheduler)`). Will be removed in v8.
- */
-export declare function empty(scheduler?: SchedulerLike): Observable<never>;
-//# sourceMappingURL=empty.d.ts.map

package/dist/compiled/inquirer/rxjs/internal/observable/forkJoin.d.ts

@@ -1,24 +0,0 @@
-import { Observable } from '../Observable';
-import { ObservedValueOf, ObservableInputTuple, ObservableInput } from '../types';
-import { AnyCatcher } from '../AnyCatcher';
-/**
- * You have passed `any` here, we can't figure out if it is
- * an array or an object, so you're getting `unknown`. Use better types.
- * @param arg Something typed as `any`
- */
-export declare function forkJoin<T extends AnyCatcher>(arg: T): Observable<unknown>;
-export declare function forkJoin(scheduler: null | undefined): Observable<never>;
-export declare function forkJoin(sources: readonly []): Observable<never>;
-export declare function forkJoin<A extends readonly unknown[]>(sources: readonly [...ObservableInputTuple<A>]): Observable<A>;
-export declare function forkJoin<A extends readonly unknown[], R>(sources: readonly [...ObservableInputTuple<A>], resultSelector: (...values: A) => R): Observable<R>;
-/** @deprecated Pass an array of sources instead. The rest-parameters signature will be removed in v8. Details: https://rxjs.dev/deprecations/array-argument */
-export declare function forkJoin<A extends readonly unknown[]>(...sources: [...ObservableInputTuple<A>]): Observable<A>;
-/** @deprecated Pass an array of sources instead. The rest-parameters signature will be removed in v8. Details: https://rxjs.dev/deprecations/array-argument */
-export declare function forkJoin<A extends readonly unknown[], R>(...sourcesAndResultSelector: [...ObservableInputTuple<A>, (...values: A) => R]): Observable<R>;
-export declare function forkJoin(sourcesObject: {
-    [K in any]: never;
-}): Observable<never>;
-export declare function forkJoin<T extends Record<string, ObservableInput<any>>>(sourcesObject: T): Observable<{
-    [K in keyof T]: ObservedValueOf<T[K]>;
-}>;
-//# sourceMappingURL=forkJoin.d.ts.map

package/dist/compiled/inquirer/rxjs/internal/observable/from.d.ts

@@ -1,6 +0,0 @@
-import { Observable } from '../Observable';
-import { ObservableInput, SchedulerLike, ObservedValueOf } from '../types';
-export declare function from<O extends ObservableInput<any>>(input: O): Observable<ObservedValueOf<O>>;
-/** @deprecated The `scheduler` parameter will be removed in v8. Use `scheduled`. Details: https://rxjs.dev/deprecations/scheduler-argument */
-export declare function from<O extends ObservableInput<any>>(input: O, scheduler: SchedulerLike | undefined): Observable<ObservedValueOf<O>>;
-//# sourceMappingURL=from.d.ts.map