node package manager


ngx-form logo


Angular Material components to set html dynamic elements configuration of @ngx-form/element package

Table of contents


Usage demonstration of a @ngx-form/material package coming soon


To install, run:

npm install --save @ngx-form/element @ngx-form/material


import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { MaterialModule } from '@angular/material';
import { FormsModule, ReactiveFormsModule } from '@angular/forms';
// internal
import { FormElementModule } from '@ngx-form/element';
import { FormMaterialModule, FormMaterialInputComponent, FormMaterialSelectComponen } from '@ngx-form/material';
  imports: [
    // external
    // internal
      types: [
          type: 'input',
          component: FormMaterialInputComponent
          type: 'select',
          component: FormMaterialSelectComponent
  declarations: [
export class ExampleModule { }


Semantic Versioning 2.0.0

Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

How should I deal with revisions in the 0.y.z initial development phase?

The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.

GIT commit




Click to donate