Signality

Signality version 0.5 is the final minor release before version 1.0. It provides a collection of approximately 76 signal-first utilities designed for Angular development.

Key features include:

• Chainable Modifiers: Use onKey modifiers to chain operations.
• Throttling Options: Support for leading and trailing options in throttling utilities.
• SSR Ready: Designed to work in Server-Side Rendering environments.
• Type Safe: Full TypeScript support for developer productivity and safety.

Signality is distributed via two main packages:

• @signality/core: Core utilities including browser APIs, element utilities, reactive helpers, and integrations for Angular router and forms.
• @signality/cdk-interop: Specialized integration for Angular CDK, providing utilities for focus monitoring, interactivity checking, and input modality detection.

The url() signal is designed to work with Server-Side Rendering (SSR):

• On the Server: The signal initializes using the router's url property. When using absolute: true, the origin is derived from the REQUEST token. It correctly handles reverse proxies by honoring X-Forwarded-Host and X-Forwarded-Proto.
• During Prerendering: Since there is no active request, the origin is unknown. The signal will fall back to a relative URL and log a warning in development.

Note: If you use absolute: true for crawler-visible metadata (like og:url), be aware that prerendered pages will contain a relative URL until they are hydrated on the client.

To maintain consistency, follow these naming patterns for TypeScript definitions:

• Types and Interfaces: Use PascalCase (e.g., BatteryOptions).
• Variables, Functions, and Properties: Use camelCase (e.g., pollingInterval).
• Configuration Objects: Append the *Options suffix (e.g., DebouncedOptions, BatteryOptions).
• Result Structures: For utilities that return an object containing multiple signals or properties, append the *Ref suffix (e.g., BatteryRef, FullscreenRef).

The cva() utility provides automatic integration with the following Angular form features:

• Reactive Forms: Compatible with FormControl, FormControlName, and FormGroup.
• Template-Driven Forms: Compatible with ngModel.
• Validators: Automatically synchronizes with Validators.required.
• State Management: Automatically syncs touched, disabled, invalid, pending, dirty, and errors states.

When running in a Server-Side Rendering (SSR) environment where the Battery Status API is unavailable, the signals in BatteryRef initialize with these safe default values:

• level → 1 (100%)
• charging → false
• chargingTime → 0
• dischargingTime → 0
• isSupported → false

When running on the server (SSR), the fps() utility provides safe default values to prevent errors:

• fps signal returns 0
• isRunning signal returns false
• start() and stop() are no-op functions

The webNotification service is safe to use in Server-Side Rendering (SSR) environments. When running on the server, the signals and methods are initialized with safe defaults to prevent errors:

• isSupported returns false.
• permission returns 'denied'.
• notification returns null.
• requestPermission is a no-op async function.
• show and close are no-op functions.

When running in a Server-Side Rendering (SSR) environment, the webShare() signals initialize with safe defaults to prevent errors:

• isSupported → false
• isSharing → false
• share → no-op async function
• canShare → returns false