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

@ngxd/core

v16.0.0

Published

NGXD is a dynamic pattern + library for Angular

Downloads

31,217

Readme

✨🦊 NGX Dynamic for Angular Ivy and Angular 7, 8, 9, 10, 11, 12, 13, 14, 15, 16+

🥳 Best way to quickly use Dynamic Components with Angular

Npm Npm Downloads Npm Downloads Weekly Travis Licence

GitHub Contributors GitHub PR GitHub Issue GitHub Stars

Use like NgComponentOutlet but with @Input and @Output auto bindings:

<ng-container *ngxComponentOutlet="component"></ng-container>

Here is a demo example showing NGX Dynamic and Angular in action.

Getting started

Step 1: Install @ngxd/core:

npm install --save @ngxd/core
# or
yarn add @ngxd/core

Note: @ngxd/core@12 only supports angular with Ivy is enabled

Note: If you want to use @ngxd/core with a specific angular version, you have to install @ngxd/core which version you need:

  • @angular/core@7 => npm install @ngxd/core@7
  • @angular/core@8 => npm install @ngxd/core@8
  • @angular/core@9 => npm install @ngxd/core@9
  • @angular/core@10 => npm install @ngxd/core@10
  • @angular/core@11 => npm install @ngxd/core@11
  • @angular/core@12 => npm install @ngxd/core@12
  • @angular/core@13 => npm install @ngxd/core@13
  • @angular/core@14 => npm install @ngxd/core@14
  • @angular/core@15 => npm install @ngxd/core@15
  • @angular/core@16 => npm install @ngxd/core@16

Step 2: Import the NgxdModule:

import { NgxdModule } from '@ngxd/core';

@NgModule({
  declarations: [ AppComponent ],
  // have import NgxdModule here 👇
  imports: [ BrowserModule, NgxdModule ],
  bootstrap: [ AppComponent ]
})
export class AppModule {}

Step 3: Use NgxComponentOutlet directly:

@Component({
  template: `
    <ng-container *ngxComponentOutlet="component"></ng-container>`
    // using @ngxd/core 👆
})
class MyComponent {  
  // your dynamic component 👇
  component = DynamicComponent;

  // 🥳 inputs and outputs will binding automatically
  @Input() entity;
  @Output() action;
}

Use cases

There are several modes of operation of the directive.

1. Binding inputs and outputs

A simple variant of binding through the parent component.

@Component({
  template: `
    <ng-container *ngxComponentOutlet="component"></ng-container>`
    // using @ngxd/core 👆
})
class MyComponent {  
  // your dynamic component 👇
  component = DynamicComponent;

  // 🥳 inputs and outputs will binding automatically
  @Input() entity;
  @Output() action;
}

Binding inputs through the context

Note: You not permitted to passing the outputs using the context. The context will be passing inputs only.

In the example below, you can see the binding through the context. This is useful when you need to display something through *ngFor. Note that the context has a higher priority than the inputs in the component.

<ng-container *ngFor="let color of colors"
  <ng-container *ngxComponentOutlet="
      component; context: { color: color }
  "></ng-container>
</ng-container>

2. Switching the component

To switch a component, you just need to overwrite it with another one.

class AppComponent {
  ngOnChanges(changes: SimpleChanges): void {
    if ('type' in changes) {
      switch (this.type) {
        case 'number':
          this.component = NumberComponent;
          break;
        case 'text':
          this.component = TextComponent;
          break;
        default:
          this.component = DefaultComponent;
      }
    }
  }
}

Switching the component using pipe and resolver

If you have a bunch of components, then you go to switch between them. To do this, you can use NgxdResolvePipe and NgxdResolver to help you isolate dynamic component selection.

<ng-container *ngxComponentOutlet="
    resolver | resolve : type
"></ng-container>

3. Lazy loading the dynamic component

If you need to load and display a dynamic component lazily, then you can use lazy import and pass it to the async pipe.

component = import('./my-lazy-component')
  .then(m => m.MyLazyComponent);
<ng-container *ngxComponentOutlet="
    component | async
"></ng-container>

Lazy loading bunch of dynamic components

You can also load a bunch of components lazily and render them.

resolver = import('./my-lazy-resolver')
  .then(m => m.myLazyResolver);
<ng-container *ngxComponentOutlet="
    resolver | async | resolve : type
"></ng-container>

4. Content projection

If you want to use the <ng-content> and pass the content to your dynamic component, you have to check the example below.

Click to here

Comparison

| Feature | NgxComponentOutlet | ComponentFactoryResolver | NgComponentOutlet | | ---------------------- | ------------------ | ------------------------ | ----------------- | | Friendliness | ⭐⭐⭐ | ⭐ | ⭐⭐ | | Dynamic Components | ✅ | ✅ | ✅ | | AOT support | ✅ | ✅ | ✅ | | Reactivity | ✅ | ✅ | ✅ | | Injector | ✅ | ✅ | ✅ | | NgModule | ✅ | ✅ | ✅ | | projectionNodes | ✅ | ✅ | ✅ | | Component Access | ✅ | ✅ | ❌ | | Lifecycle OnChanges | ✅ | ⭕️ manually | ❌ | | Binding @Input() | ✅ | ⭕️ manually | ❌ | | Binding @Output()| ✅ | ⭕️ manually | ❌ | | Activate Event | ✅ | ⭕️ manually | ❌ | | Deactivate Event | ✅ | ⭕️ manually | ❌ |

API

| Input | Type | Default | Required | Description | | ----------------------------------------- | -------------------------- | ------- | -------- | ----------- | | [ngxComponentOutlet] | Type<any> | n/a | yes | | | [ngxComponentOutletContext] | any | n/a | no | | | [ngxComponentOutletInjector] | Injector | n/a | no | | | [ngxComponentOutletContent] | any[][] | n/a | no | |

| Output | Type | Description | | ----------------------------------------- | -------------------------- | ----------- | | (ngxComponentOutletActivate) | any | | | (ngxComponentOutletDeactivate) | any | |