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-annotate-namespace-collision

v1.2.1

Published

A plugin for ng-annotate to enable Angular namespace collision detection

Downloads

7

Readme

A minimal plugin to ngAnnotate for detecting Angular namespace collisions.

i.e. if you have the following in one area of your code:

angular.module('encore.cloud')
    .controller('MyFirstCtrl')

and this is another area:

angular.module('encore.ticketing')
    .factory('MyFirstCtrl')

an error will be raised.

To use this module with ngAnnotate, import it with require and pass to ngAnnotate with the plugin option, i.e.

const ngAnnotate = require("ng-annotate");
const nameCollision = require('../src/nameCollisionPlugin.js');

ngAnnotate(String(fs.readFileSync(filename)), {
    plugin: nameCollision
});

This will also work fine as a gulp task. An example of this is:

gulp.task('compile:detectCollision', function () {
    var scriptSourcePaths = [
        srcPath + '/src/**/*.js',
        srcPath + '/src/app.js',
        '!' + srcPath + '/src/**/*.spec.js',
    ];
    nameCollision.reset();
    return gulp.src(scriptSourcePaths)
        .pipe(plugins.plumber(function (err) {
            plugins.util.log(err.message);
            process.exit(1);
        }))
        .pipe(plugins.ngAnnotate({
            plugin: nameCollision
        }));
});//compile:detectCollision

Notice that when used in a gulp task, we call nameCollision.reset(). This is to account for something like gulp server, which usually keeps running and reruns all the tasks whenever your source code changes. In that situation, gulp does not reload the plugins, so the same instance of nameCollision is being used on every run. We want to make sure that the names discovered on the previous run are all cleared out, hence calling nameCollision.reset()