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

angular-beacon

v0.0.3

Published

Angular.JS directive which executes a callback when the view is fully rendered.

Downloads

8

Readme

angular-beacon

Lighthouse

In Angular there's no way to know when it has finished rendering items on the screen. Controllers emit $viewContentLoaded and directives call postLink() when Angular has finished cloning the template, but that doesn't mean that DOM nodes were created yet, not that the page has been fully rendered.

Wouldn't it be nice to be told when the page has been fully rendered? Unfortunately, Angular doesn't yet provide us a way to know that.

Some people suggest to wrap your DOM-interacting code inside a couple of nested $timeout calls. Others suggest to check the $digest loop and do your stuff when the queue is empty. The former solution doesn't always work and the latter may suffer from starvation in case you have a constant stream of events coming from another source.

We know this is not the Angular way of doing things but, sometimes, it's unavoidable (additionally, we had to go this route in a couple of projects already).

Angular-Beacon repeatedly checks the DOM until all the elements you need become available (it will try for up to five seconds), then it invokes a callback function (which must have been defined in your scope) in which you can do all the DOM manipulation you want.

How to use

Add angular-beacon to the list of dependencies in your Angular.JS application:

    angular.module('myapp', [
        'ngRoute',
        // ...
        'angular-beacon'
    ]);

Create a callback function in your controller's or directive's scope. As a bonus, all elements found are passed to your callback within an object (see below for details).

    angular.module('myapp').controller('MyController', function ($scope) {
        scope.myCallback = function(cache) {
            console.log('DOM Ready!');
        };
    });

In your view or template, add a reference to the beacon directive, towards the end of it:

    <div class="my-panel">
        ...
    </div>
    <button>Push button</button>
    <beacon waitfor=".my-panel, button" onready="myCallback"></beacon>

myCallback will be called as soon as .my-panel and button appear on the page (as DOM nodes at least).

That is: each beacon directive instances expects two attributes:

  • onready is the name of callback function defined inside the current Angular.JS scope which will be called when the DOM is ready.
  • waitfor: A comma-separated list of CSS selectors, the same you would use with jQuery. The selector is normalized, replacing all non-alphanumeric characters with underscores and used as the property name holding the cached value in the cache object passed to your callback.