npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

rxjs-conduit

v4.3.1

Published

A special kind of RxJS Subject, which preserves the last value emitted for late subscribers.

Downloads

1,386

Readme

Conduits!

A special kind of RxJS Subject, which preserves the last value emitted for late subscribers.

Dude just use signals???

  • Angular's use of RxJS goes back further, so I'd rather use that.  Computed signals are also too "magical" for me.
  • I find this way of doing things more intuitive.  If you prefer something else, do that and save yourself the dependency!

Features

  • 🔄 Late Subscriber Catch-Up: Never miss a value again!
  • 💪 Flexible: Easy to use even with minimal planning done in advance!
  • 🎯 Type-Safe: Full TypeScript support!
  • 🛠 Framework Compatible: Use the subclasses like NgConduit for easy cleanup on component destruction!

Installation

npm install rxjs-conduit

Usage

Basic Vanilla Usage

import { Conduit } from 'rxjs-conduit/vanilla';

const source = new Conduit<string>();

// Use .then for single-shot observations that auto-unsubscribe
source.then(value => console.log(`${value} world`));

source.next("hello"); // "hello world"
source.next("hi");

// Late subscriptions get updated with the last event
source.subscribe(value => console.log(`${value} npm!`)); // "hi npm!"

source.next("bye"); // "bye npm!"
source.complete();

Angular Integration

import { Component, ViewChild, Input } from '@angular/core';
import { interval } from 'rxjs'

// NgConduits inject a DestroyRef, and know when to clean themselves up!
import { NgConduit } from 'rxjs-conduit/angular';

type Thing = {
    data$: Conduit<string>
}

@Component({
    selector: 'app-thing-view',
    templateUrl: './thing-view.component.html',
    styleUrls: ['./thing-view.component.scss']
})
export class ThingViewComponent {

    /*
        Ever tried to access something only for Angular to be like,
        > "that's not ready in this lifecycle hook yet!!!"
        Hook a setter to a conduit and never worry again.
    */
    @ViewChild(ChildComponent)
        protected set child(c: ChildComponent){ _child$.next(c); }
        protected get child(){ return _child$.value as ChildComponent }
    private _child$ = new NgConduit<ChildComponent>();

    /*
        In one case, I needed nested reactivity on an Angular input.
        For this, .inner() is a fantastic tool.
    */
    @Input()
        public set thing(t: Thing){ this._thing$.next(t) }
        public get thing(){ return this._thing$.value as Thing }
    private _thing$ = new NgConduit<Thing>();

    // use this as normal, it will update both sources
    protected thingData$ = _thing$.inner( (thing) => thing.data$ );

    constructor(){
        // This will run as soon as Angular decides to set up the child
        _child$.then( child => child.doSomething() );
    }
}

API: Conduit

(Things that Subject can already do are omitted.)

new Conduit(first?: T)

Creates a new conduit, optionally with an initial value.

Conduit.derived(sources, formula): ReadonlyConduit

Creates a conduit whose value is derived using a formula and a set of source conduits.
Completes when all sources complete and errors if any source errors.

subscribe(observer): Subscription

Adds a subscription to this conduit, which will receive reactive updates.

inner(getter): Conduit

Creates a special "proxy" conduit based on the getter and value(s) of this conduit.

then(callback): Subscription

Similar to subscribe, but it only runs once then cleans up the subscription.

unsubscribe(): void

Removes all subscribers to this conduit without notifying them.

splice(source, config?): Conduit

Adds a source to this conduit, which will feed it values reactively.  Returns self.

unsplice(name?): boolean

Disconnects a previous spliced source from this conduit, if it was named.
Pass no name to unsplice everything.

sealed: boolean

True after it completes or errors.

value: T

Returns the most recent value, or Conduit.EMPTY if there isn't one yet.

valueOrDefault(fallback): T

Returns the conduit's value, or returns the fallback if it's empty.

valueOrThrow(reason): T

Returns the conduit's value, or throws the reason if it's empty.

flush(): void

Sets the conduit back to Conduit.EMPTY without notifying subscribers.

Bonus API: Gate

new Gate()

Creates a semaphore-like object which is callable and returns its value.
Can be passed directly to RxJS's filter operator to gate an observable source!

run(section): T

Runs the section if the gate isn't currently running anything else.
Returns the result, or Gate.BLOCKED if it didn't run.

open: boolean

Is the gate ready to run something?

License

MIT License.

Copyright © 2024; Fasteroid

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.