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 🙏

© 2025 – Pkg Stats / Ryan Hefner

ng-api-helper

v1.2.6

Published

An Angular CLI helper to generate Api Helper files with destroyable components and dynamic API call helpers, reducing manual copy-pasting and promoting clean, maintainable code.

Readme

📘 ng-api-helper — User Guide

🚀 Overview

ng-api-helper is a lightweight Angular CLI tool designed to generate reusable helper files that simplify API calls and subscription management. It provides two essential utilities:

✅ DestroyableComponent

A base component class that automatically manages subscription cleanup using Angular’s lifecycle.
👉 To use loadApi, your component must extend DestroyableComponent.

✅ loadApi

A helper function that wraps any API call and handles the entire lifecycle: success callback, error handling, finalize logic, and automatic cleanup when the component is destroyed.
This removes repetitive boilerplate and promotes cleaner, more maintainable Angular code.


📦 Installation & Usage

1️⃣ Install globally

npm install ng-api-helper

2️⃣ Generate helper files Run the CLI inside your Angular project:

ng-api-helper

This will create the following files:

destroyable-component.ts

api-call-helper.ts

These files are immediately ready to use.

🧱 Component Requirement

To use loadApi, your component must extend the generated DestroyableComponent:

import { DestroyableComponent } from './destroyable-component';

export class MyComponent extends DestroyableComponent {
  constructor() {
    super();
  }
  // your logic here
}

This ensures automatic subscription cleanup without manually unsubscribing.

🎯 Example: Dynamic API Call Using loadApi

loadItems() {
  this.loading = true;

  loadApi(
    // Any API call (replace with your own Observable)
    this.myService.getItems(),
    this.destroy$,

    // SUCCESS
    (response) => {
      this.items = response;

      if (this.dataSource) {
        this.dataSource.data = response;
      }
    },

    // ERROR
    (error) => { this.notificationService.showError(error); },

    // FINALIZE
    () => { this.loading = false; }
  );
}

🎉 Benefits

No manual unsubscribe needed

Clean and consistent API handling

Centralized success, error, and finalize logic

Automatic memory leak prevention

Scales perfectly for medium and large Angular applications

🔖 Notes

Always extend DestroyableComponent when using loadApi.

Replace this.myService.getItems() with your actual service call.

this.destroy$ is provided by DestroyableComponent and ensures cleanup.