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-forever

v1.2.5

Published

Angular optimization and convention checker that helps you find and fix common issues in your Angular applications.

Downloads

74

Readme

ngForever

Angular optimization and convention checker that helps you find and fix common issues in your Angular applications. Works great as a pre-commit hook!

Features

  • 🔍 Automatically detects optimization opportunities
  • ⚡ Improves application performance
  • 🎯 Enforces best practices and conventions
  • 🛠️ Customizable to your project needs
  • 📋 Detailed reporting with file and line references

Installation

You can install ngForever using npm:

npm install ng-forever

Or run it directly using npx:

npx ng-forever

Usage

Run ngForever in your Angular project directory:

ng-forever [options]

Command Line Options

| Option | Description | Default | |----------------------|------------------------------------------|-------------------| | --logLevel | Set the logging verbosity | INFO | | --skipCommented | Skip checking commented code | false | | --path | Set the directory path to check | Current directory | | --showFixSuggestion | Display suggestions for fixing issues | true | | --exportPdf | Exports a designed pdf (More at docs/reporter) | false |

Log Levels

The following log levels are available:

  • INFO: Standard information
  • WARN: Warning messages
  • ERROR: Error messages
  • DEBUG: Detailed debug information
  • SYSTEM: System-level messages

Jobs

ngForever runs a series of jobs to check your Angular application. Each job focuses on specific optimization or convention checks.

Currently Available Jobs

FindNgForWithoutTrackByCallbackJob

Detects *ngFor directives that don't implement a trackBy callback function, which can lead to performance issues.

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

To run the app locally for development:

Option One (Build and Run):

Bash

npm run build
node .dist/index.js --path "some-directory-for-testing"

You can add other options as needed. Replace "some-directory-for-testing" with the path to the directory you want to analyze.

Option Two (Debugging):

Use a debugger (e.g., in your IDE) and update the arguments with the relevant options.

License

MIT - See LICENSE file for details

Support

If you encounter any issues or have questions, please file an issue on the GitHub repository. Example output: