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

ngx-host-observable

v0.0.0-watch

Published

An angular library for automated and secure obseravable suscribing and unsubscribing.

Downloads

3

Readme

NgxHostObservable

An angular library for automated and secure obseravable suscribing and unsubscribing.

Getting Started

Installation

npm install ngx-host-observable
yarn add ngx-host-observable
pnpm add ngx-host-observable

Example Usage

Just decorate your observable property with @HostObservable

import { HostObservable } from 'ngx-host-observable';
import { interval } from 'rxjs';

@Component({ ... })
export class MyComponent {
	@HostObservable()
	timer$ = interval(1000).pipe(
		tap(seconds => console.log(seconds + ' seconds has passed'))
	);
}

That's all! The observable is going to be suscribed on the component creation and unsuscribed on component destroy.

Recommended

Accessing Observable

It is possible to reuse the same observable within your application

import { HostObservable } from 'ngx-host-observable';
import { interval, scan } from 'rxjs';

@Component({ ... })
export class MyComponent implements OnInit {
	@HostObservable()
	timer$ = interval(1000).pipe(tap(console.log));

	loading$?: Observable<boolean>;

	ngOnInit() {
		// Complete loading when timer$ reaches 10 seconds
		loading$ = this.timer$.pipe(
			scan(times => times + 1, 0), 
			filter(times => times === 10), 
			map(() => false), 
			startWith(true), take(2)
		);
	}
}

Warning

Even though it's possible to re use the same decorated observable, there is one case where you not supposed to use it.

Because of the way of how decorators work in Typescript, in order to access the decorated observable is necessary to stablish getter and setter methods for the property

Object.defineProperty(target, propertyKey, {
	set: observable$ => {
		...
	},
	get: () => ...
});

This does not have any impact on typescript itself and you can get the value safely, but in angular templates, getting value from getters and functions is a huge performance killer.

@Component({
	...,
	template: '<span>{{ timer$ | async }} seconds passed</span>'
})
export class MyComponent implements OnInit {
	@HostObservable()
	timer$ = interval(1000).pipe(tap(console.log));
}

This is because angular reevaluates templates bindings on each tick. You can read more about here.

To solve this problem just remove the decorator. All is going to work the same because async pipe suscribes and unsuscribes automatically your observable.

@Component({
	...,
	template: '<span>{{ timer$ | async }} seconds passed</span>'
})
export class MyComponent implements OnInit {
	timer$ = interval(1000).pipe(tap(console.log));
}