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

roberthodgen-logger

v1.0.0

Published

Improved logger for AngularJS projects.

Downloads

2

Readme

angular-logger

Improved logger for AngularJS projects.

Features

  • Multiple (and customizable) log levels.
  • Log history (up to n records).
  • Hooks for error handling.

Usage

Include the angular-logger.js file in your project:

<script src="angular-logger.js"></script>

Make roberthodgen.angular-logger available in your modules, e.g.:

var app = angular.module('myAppOrModule', ['roberthodgen.angular-logger']);

Creating log entries

Log.debug('My debug message here...');

Where debug property of Log should be switched to your defined level.

Accessing history

Log.debug.history

An Array with a given level's history is set as the history property of each level.

Using hooks

var deregisterFn = Log.debug.addHook(function (entry) {
  // Code to handle hook callback...
});

A hook may be added via calling addHook on a given log level. The function will be called every time the level receives a new entry.

Note: deregisterFn is a function that removes the hook. It should be called when the hook is no longer needed. E.g. on a controller's $scope $destroy event:

$scope.$on('$destroy', function () {
  deregisterFn();
  // Other cleanup code...
});

Defining custom log levels

Custom log levels can be defined at the config state using the LogProvider.

app.config(['LogProvider', function (LogProvider) {
  LogProvider.LOG_LEVELS = ['info', 'debug', 'warn', 'error'];
}]);

A working example of defining custom levels can be seen in example/app.js.

A custom log level may also accept an Object in the following form:

{
  name: 'debug',
  hooks: [
    function (entry) {
      // Code to handle entry...
    }
  ]
}

Where the name property is the name associated with the log level and hooks is an Array of callback hook functions.

NOTE: When adding hooks during config no deregister functions are saved or returned!

Requirements

Ensure all NPM dependencies are installed and updated.

$ npm install

Install Karma

$ npm install -g karma-cli

Tests

$ karma run

All unit tests are located in the test directory.

Getting access to Log from browser console

TODO.