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

@blaugold/angular-logger

v0.0.3

Published

Logger for Angular 2 Apps.

Downloads

10

Readme

Angular Logger

CircleCI

npm version

Logger for Angular 2 Apps.

Installation

    npm i --save @blaugold/angular-logger

Usage

Include the LoggerModule and the ConsoleWriterModule at the root module.

@NgModule({
    imports: [
        LoggerModule.forStd(),
        ConsoleWriterModule.forRoot()
    ]
})
export class AppModule {
}

In your components, directives, pipes and services get the Logger through DI.

@Injectable()
export class MyService {

    constructor(private log: Logger) {}
    
    getSome() {
        this.log.trace('Getting something for MyService')
    }
}

To change the log level at which the logger emits logs, type in the console logat.trace to set the logger to log level Trace for example. Per default the logger is set to Info. You can also permanently change the log level:

    LoggerModule.forStd(new LoggerDef().level(LogLevel.Warn))

Noop Logger

When testing classes which use a logger, but you are not interested in what is logged, add LoggerModule.forStd() to the testing module. As long as there is no log consumer like the ConsoleWriterModule imported the LoggerModule will inject a noop logger for the Logger token.

Package Logger

Packages which are included in other apps to provide some functionality can make use of aux loggers in their classes:

    export const myPkgLogger = new LoggerDef('MyPkg')
    
    @Injectable()
    export class MyService {
        constructor(@Inject(myPkgLogger) log: Logger) {
            log.info('MyService was instantiated')
        }
    }
    
    @NgModule({
        imports: [
            LoggerModule.forAux([myPkgLogger])
        ]
    })
    export class MyPkgModule {
    }

Consumers of this package can use myPkgLogger to set the log level of the package's logger. If the consuming app or package does not register a LogConsumer the classes are injected with a noop logger.