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

@act-spec/component-angular

v0.2.0-rc.1

Published

PRD-303 Angular binding for the ACT (Agent Content Tree) v0.1 component contract (PRD-300). Implements the three Angular declaration patterns (component static-field `static act = {...}`, service-based `ActContractService.register({...})`, and the page-le

Downloads

46

Readme

@act-spec/component-angular

Angular binding for the ACT component contract. Bridges Angular component trees to the framework-agnostic NodeDraft shape exported by @act-spec/component-contract.

Implements the three Angular declaration patterns:

  • component static field — static act = { … },
  • service-based — ActContractService.register({ … }),
  • page-level boundary — *actSection="contract" structural directive or the <act-section> component form.

The ActCollectorService is provided component-locally (never 'root') for SSR-walk extraction. The canonical SSR walker uses @angular/platform-server.renderApplication and waits for ApplicationRef.isStable. Variant replay constructs a fresh ApplicationRef + EnvironmentInjector per variant. Render-time errors surface through Angular's ErrorHandler provider as truncated + secret-redacted placeholders. The BindingCapabilities const reflects only what v0.1 ships.

Note: no v0.1 leaf generator depends on this binding directly. The documented integration path is via @act-spec/cli running over an Angular Universal app. A future Angular-native generator (deferred to v0.2) would consume the same extractRoute() API.

Status

ACT v0.1 internal hand-test candidate. Public release lands at v0.2.

Install

Unpublished in v0.1. Consume via the workspace:

// package.json
{ "dependencies": { "@act-spec/component-angular": "workspace:*" } }

Usage

Static field on a component class:

import { Component } from '@angular/core';
import type { AngularComponentWithAct } from '@act-spec/component-angular';

@Component({ selector: 'pricing-table', templateUrl: './pricing.html' })
export class PricingTable implements AngularComponentWithAct {
  static act = {
    type: 'marketing:pricing',
    title: (p: Inputs) => p.heading,
    contentBlocks: (p: Inputs) => p.tiers.map(toBlock),
  };
}

Service-based registration:

import { Component, inject } from '@angular/core';
import { ActContractService } from '@act-spec/component-angular';

@Component({ selector: 'faq-section', templateUrl: './faq.html' })
export class FaqSection {
  private readonly act = inject(ActContractService);
  constructor() {
    this.act.register({
      type: 'marketing:faq',
      contentBlocks: () => this.items.map(toBlock),
    });
  }
}

Generators call extractRoute:

import { extractRoute, angularBinding } from '@act-spec/component-angular';

const drafts = await extractRoute({
  pageContract: { /* … */ },
  appModule: AppModule,
  variants: [/* … */],
});

Conformance / what's tested

Every public API has a citing test in the package's test suite, including the Angular 17+ floor (assertAngular17Plus), the collector scope check, contract-version pinning, and the placeholder + redaction contract. The conformance gate runs @act-spec/validator against the extracted nodes.

pnpm -F @act-spec/component-angular conformance

Peer dependencies

| Peer | Range | | --- | --- | | @angular/core | >=17 <21 | | @angular/platform-server | >=17 <21 |

Both peers are optional from npm's perspective; the binding only requires them at extraction time.

Links