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 🙏

© 2024 – Pkg Stats / Ryan Hefner

ng-log

v1.3.0

Published

ng-log is a simple Log class for Angular which wraps the console log methods, and write

Downloads

29

Readme

ng-log

ng-log is a simple Log class for Angular which wraps the console log methods, and write

Installation

npm install ng-log --save

or

yarn add ng-log

Basic Usage

The basic usage will be to construct a Log instance, passing an argument which is a context value that will be prepended to each log message.

export class SomeComponent {

    private log: Log = new Log(SomeComponent.name)

    constructor() {}

    public doTheThing() {
       this.log.log('Doing the thing')
    }
}

The Log class has the @Injectable annotation, so you can also add it in your constructor if you added it in your app module providers.

export class SomeComponent {

    constructor(private log: Log) {
        this.log = log.withContext(SomeComponent.name)
    }

    public doTheThing() {
       this.log.log('Doing the thing')
    }
}

Note that if you use SomeComponent.name as the context then that will probably get mangled to the minified class name. If you have console logging enabled in production and want the proper name with a prod optimised build then you will need to use a string instead of a .name reference.

Advanced usages

In a production app you may want to turn off logging to the console. In particular for our Ionic/Cordova mobile apps the system browser logs aren't going to be seen by anyone so the logging can be disabled.

class MyApp {

    initializeApp() {
        this.platform.ready().then(() => {
            if(environment.isProduction()) {
                Log.logToConsole = false
            }
        })
    }

}

All log messages logged will added to the static Observable property $logEntry

An important use case for using this Log class is being able to subscribe to the $logEntry observable so you can perform more interesting actions, such as posting error messages to your server for error reporting.

An example LogSubmitter is included in the /example folder which submits error messages, along with the recent log message history, and other information such as the userId, code version and platform version.