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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@planeasyinc/fe-angular

v0.1.10

Published

Angular 17+ standalone components for form engine. Built with partial-Ivy compilation for optimal bundle size and performance.

Readme

@planeasyinc/fe-angular

Angular 17+ standalone components for form engine. Built with partial-Ivy compilation for optimal bundle size and performance.

TL;DR - Quick Reference

# Install
npm install @planeasyinc/fe-angular @planeasyinc/fe-core

# Use in component
import { FeFieldHost } from '@planeasyinc/fe-angular';
import { createEngine } from '@planeasyinc/fe-core';

# Build library
pnpm run build

# Publish
pnpm publish --registry=https://npm.pkg.github.com

What is @planeasyinc/fe-angular?

@planeasyinc/fe-angular is an Angular library that provides 32+ form control components for building dynamic forms. It works with @planeasyinc/fe-core to manage form state, validation, and value changes.

Key features:

  • ✅ 32+ form controls (text, number, select, date, file upload, etc.)
  • ✅ Standalone Angular 17+ components
  • ✅ Dynamic form rendering via FeFieldHost
  • ✅ Type-safe with TypeScript
  • ✅ Built with NG-ZORRO Ant Design components

Requirements

  • Angular: 17.0.0 or higher
  • TypeScript: 5.4.x (5.2+ minimum)
  • RxJS: 7.8.0 or higher
  • Node.js: 18+ (for building)
  • NG-ZORRO Ant Design: 17.x (peer dependency)
  • @angular/animations: 17.x (peer dependency)
  • date-fns: ^2.0.0 (peer dependency)

Installation

From GitHub Packages

  1. Create .npmrc in your project root:
@planeasyinc:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=YOUR_GITHUB_TOKEN
  1. Install packages:
npm install @planeasyinc/fe-angular @planeasyinc/fe-core ng-zorro-antd@17 @angular/animations@17 date-fns
# or
pnpm add @planeasyinc/fe-angular @planeasyinc/fe-core ng-zorro-antd@17 @angular/animations@17 date-fns

Note: You need a GitHub Personal Access Token with read:packages scope.

NG-ZORRO Setup

After installing, you must configure NG-ZORRO in your Angular app. See the NG-ZORRO Setup Guide for detailed instructions.

Quick setup:

  1. Import BrowserAnimationsModule in your app module
  2. Provide NZ_I18N with locale (e.g., en_US)
  3. Add NG-ZORRO styles to your global stylesheet
  4. (Optional) Register icons from @planeasyinc/fe-angular/icons

From Workspace (Development)

If using pnpm workspaces:

{
  "dependencies": {
    "@planeasyinc/fe-angular": "workspace:*",
    "@planeasyinc/fe-core": "workspace:*"
  }
}

Quick Start

1. Import and Use Standalone Components

import { Component } from '@angular/core';
import { FeTextControl, FeNumberControl } from '@planeasyinc/fe-angular';
import { createEngine } from '@planeasyinc/fe-core';

@Component({
  selector: 'app-form',
  standalone: true,
  imports: [FeTextControl, FeNumberControl],
  template: `
    <fe-text [engine]="engine" path="name" [label]="'Name'" />
    <fe-number [engine]="engine" path="age" [label]="'Age'" />
  `
})
export class FormComponent {
  engine = createEngine({
    fields: [
      { type: 'text', name: 'name', label: 'Name' },
      { type: 'number', name: 'age', label: 'Age' }
    ]
  });
}

2. Use FieldHost for Dynamic Forms

import { Component } from '@angular/core';
import { FeFieldHost } from '@planeasyinc/fe-angular';
import { createEngine, type FeControlConfig } from '@planeasyinc/fe-core';
import { CommonModule } from '@angular/common';

@Component({
  selector: 'app-dynamic-form',
  standalone: true,
  imports: [FeFieldHost, CommonModule],
  template: `
    <fe-field
      *ngFor="let field of fields"
      [engine]="engine"
      [control]="field"
    />
  `
})
export class DynamicFormComponent {
  engine = createEngine({
    fields: [
      { type: 'text', name: 'email', label: 'Email' },
      { type: 'select', name: 'country', label: 'Country', meta: { options: [...] } }
    ]
  });

  fields: FeControlConfig[] = this.engine.config.fields;
}

3. Access Form Values

// Get all values
const values = this.engine.values.getAll();

// Get single value
const email = this.engine.values.get('email');

// Listen to changes
this.engine.on('valueChanges', (values) => {
  console.log('Form values changed:', values);
});

// Submit
const isValid = this.engine.validate();
if (isValid) {
  const formData = this.engine.values.getAll();
  // Submit formData
}

Registry Overview

The library uses a registry pattern to map control types to Angular components:

import { getRenderer, hasRenderer, ANGULAR_RENDERERS } from '@planeasyinc/fe-angular';

// Check if a control type is supported
if (hasRenderer('text')) {
  const Component = getRenderer('text');
  // Component is FeTextControl
}

// Access full registry
console.log(ANGULAR_RENDERERS); // Record<FeControlType, Type<any>>

FeFieldHost uses this registry to dynamically render controls based on control.type.


Available Controls

See docs/controls.md for the complete catalog of 32+ controls.

Categories:

  • Text inputs (text, email, phone, password, textarea)
  • Numbers (number, number-slider, number-operations)
  • Selection (select, multiselect, radio, checkbox, toggle)
  • Date/Time (date, datetime, time, date-triplet)
  • Structural (array, dict, group, object)
  • File uploads (attachment, file)
  • Special (button, chat, infoscreen, mask, json)

Versioning & Releases

We follow Semantic Versioning:

  • Major (x.0.0): Breaking changes
  • Minor (0.x.0): New features, backward compatible
  • Patch (0.0.x): Bug fixes, backward compatible

Current version: 0.1.2

Release tags:

Breaking changes:

  • Angular 17+ required (no support for Angular 16 or lower)
  • TypeScript 5.4.x recommended (5.2+ minimum)

Documentation


Support

  • Issues: GitHub Issues (if public) or internal ticketing
  • Questions: Contact the team lead

License

Proprietary - Internal use only