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-utilities/ngx-let

v0.0.3

Published

[![npm version](https://badge.fury.io/js/%40ngx-utilities%2Fngx-let.svg)](https://www.npmjs.com/package/@ngx-utilities/ngx-let)

Downloads

10

Readme

ngx-let

npm version

The *ngxLet directive allows you unwrap an observable using async without hiding the DOM element if the observable emits a falsy value. You can do this using ng-template and *ngTemplateOutlet by setting the context on the outlet, but the *ngxLet directive hides that implementation complexity.

Installation

To install this library, run:

npm install @ngx-utilities/ngx-let --save -or- yarn add @ngx-utilities/ngx-let

and then import and export NgxLetModule in your Angular SharedModule:

// shared.module.ts

import { NgxLetModule } from '@ngx-utilities/ngx-let';

@NgModule({
  imports: [
    NgxLetModule
  ],
  exports: [
    NgxLetModule
  ]
})
export class SharedModule { }

Example use-case

Say you are writing your site's layout and you want to show whether the user is logged in or not in both the header and the footer.

<header>
  ... header content
  You {{ loggedIn | async ? 'are' : 'are not'}} logged in.
  ... more header content
</header>

<main>
  <router-outlet></router-outlet>
</main>

<footer>
  ... footer content
  You {{ loggedIn | async ? 'are' : 'are not'}} logged in.
  ... more footer content
</footer>

That seems easy enough. But you are creating two subscriptions to the loggedIn observable. Duplicate subscriptions lead to obscure bugs and possible perfomance issues, so it's better to subscribe only once. We can subscribe only once using *ngIf:

<ng-container *ngIf="loggedIn | async; let loggedIn">
  <header>
    ... header content
    You {{ loggedIn ? 'are' : 'are not'}} logged in.
    ... more header content
  </header>

  <main>
    <router-outlet></router-outlet>
  </main>

  <footer>
    ... footer content
    You {{ loggedIn ? 'are' : 'are not'}} logged in.
    ... more footer content
  </footer>
</ng-container>

Uh oh. Now the page is black for users who aren't logged in! Let's fix it using ng-template.

<ng-container *ngTemplateOutlet="layoutTemplate; context: { loggedIn: loggedIn | async }">
</ng-container>

<ng-template #layoutTemplate let-loggedIn="loggedIn">
  <header>
    ... header content
    You {{ loggedIn ? 'are' : 'are not'}} logged in.
    ... more header content
  </header>

  <main>
    <router-outlet></router-outlet>
  </main>

  <footer>
    ... footer content
    You {{ loggedIn ? 'are' : 'are not'}} logged in.
    ... more footer content
  </footer>
</ng-template>

The *ngTemplateOutlet directive is super useful for content projection, but using it for this particular use-case seems messy. Enter *ngxLet:

<ng-container *ngxLet="loggedIn | async; let loggedIn">
  <header>
    ... header content
    You {{ loggedIn ? 'are' : 'are not'}} logged in.
    ... more header content
  </header>

  <main>

  </main>

  <footer>
    ... footer content
    You {{ loggedIn ? 'are' : 'are not'}} logged in.
    ... more footer content
  </footer>
</ng-container>

License

MIT © Kevin Phelps