ng-forge — dynamic forms for Angular

provideDynamicForm(...) is variadic — it takes a list of field-type registrations. Spread an adapter's bundle (...withMaterialFields() registers all the built-in Material fields), then append your own: { name: 'rich-text', loadComponent: () => import('./rich-text'), mapper: valueFieldMapper }. Your component is a plain standalone Angular component that receives Signal Forms' FieldTree<T> via input.required(). See Adding custom fields.

Use a targetProperty: 'options' derivation with source: 'http'. Pass the URL (or query params with field-value interpolation), a responseExpression that maps the response to { value, label }[], and dependsOn if it should re-fetch when another field changes. See Async data.

Yes. Different package names, different injection tokens, different component selectors. Install ng-forge, port one form at a time, deprecate formly when nothing imports @ngx-formly/*.

FormConfig is a plain TypeScript object — extract reusable pieces (a field, a validator entry, a default props object) as named consts and import them. For application-wide defaults, use defaultProps on the form or adapter-level providers like withMaterialFields({ appearance: 'fill' }).

Labels, placeholders, and hint text accept string | Signal<string> | Observable<string> — wire them to your i18n service. Validation kinds map to messages via per-field validationMessages or form-level defaultValidationMessages. See the i18n guide.

The (submitted) event emits the form value directly — JSON.stringify(value) is enough. To strip hidden, disabled, or readonly fields, set excludeValueIfHidden (and the sibling options) on the form config or via withValueExclusionDefaults(). See Value exclusion.

Yes by default — ng-forge keeps hidden values live so a hide/show toggle preserves what the user typed. Opt out with excludeValueIfHidden: true to strip them at submission output time, or wire a derivation that clears the value when the hide condition is true (formly's resetOnHide behaviour).

Debouncing happens on the consumer side: set trigger: 'debounced' and debounceMs on the derivation, condition, or HTTP validator that reads the value. The Signal Forms substrate commits on every change — there is no updateOn: 'blur' equivalent today, so debouncing the consumers is the closest workaround for blur-style commit timing.

Yes — every adapter is built on the same public surface, so you can ship a custom adapter for Kendo, NG-ZORRO, NativeScript, or an in-house design system. See Building an adapter.

No. ng-forge is built on Angular Signal Forms (@angular/forms/signals). The primitive is FieldTree<T> — a signal-native tree of value, validity, dirty/touched state, and errors. Reactive Forms still works in Angular, but the two systems don't share types or APIs.

Not today — file inputs are not a built-in field type in any adapter. Implement one as a custom field with valueFieldMapper: a standalone component that renders an <input type='file'>, captures File | FileList into the field's value, and (optionally) uploads to your backend via a custom validator or value-derivation. See Adding custom fields.

Yes. The library is built around Angular signals (no module-scoped mutable state), and the docs site itself is server-rendered with full incremental hydration through the @defer blocks that wrap heavy components. If you author a custom field type, follow the same rule the core library follows: keep all per-form state in DI-scoped services, never in module-level singletons.

No automated migration tool today — port manually. The concept-mapping table in the migration guide is the closest thing to a porting cheatsheet; the MCP server lets an LLM in your IDE generate large chunks of the new config from a description of the old one. A codemod is on the wishlist but not committed work.

ng-forge is a batteries-included framework — the engine itself is intentionally large because it ships the full validation, conditional logic, derivation, schema, and array-management surface needed for API-driven forms (where the form shape is unknown at build time). What you do not pay for upfront: every adapter loads its field components via dynamic import() per field type, so a form that only uses input and select only fetches those two component bundles. UI adapters (Material, PrimeNG, Bootstrap, Ionic) themselves are independent packages — only the one you install ships.

Angular 21+ (signal-native APIs depend on it). Browser-wise, ng-forge supports the same matrix as Angular 21 — modern evergreen browsers (Chrome / Edge / Firefox / Safari current and previous major). No IE 11.