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

remove-angular-modules-loader

v1.1.3

Published

remove the module system from angular via a webpack loader

Downloads

224

Readme

remove-angular-modules-loader

angular modules suck when you already have require. lets remove them by putting everything into a module called 'app'

Usage

npm install remove-angular-modules-loader

in your webpack config's loaders section:

{
    test: /\/angular(.min)?\.js$/,
    loader: 'remove-angular-modules'
},

moduleName is optional, default module name is 'app'. It is recommended that you update your html with this module name.

Query params

  • moduleName name of the module that everything will go into
  • whiteList[] allow these modules to be created under their original module name
  • blackList[] ignore creation of these modules. no code registered to these modules will ever run
  • testing valid values: 'unit' or 'e2e'. ngMock contains both types of modules, so this will properly configure the blacklist property for you. Use this only when testing with ngMock or ngMockE2E

example

{
    test: /\/angular(.min)?\.js$/,
    loader: 'remove-angular-modules?moduleName=hourlynerd&whiteList[]=foo&whiteList[]=bar&blackList[]=skillbridge&testing=e2e'
}

How it works

It patches angular to put everything into a single module*. You no longer need to define module dependencies when creating modules, or names for that matter.

    • protractorBaseModule_ remains its own module because otherwise protractor tests don't work. (you can still blacklist it)

This is now valid:

angular.module().controller('MyController', ....)

but your old code will still work too.

Now you can focus on requiring angular things with webpack just like you require everything else.

Secret Sauce

The magic happens when we append the following script to the end of angular.js (ok, its a bit longer now...)

(function(a, moduleName) {
    //remove angular module system, everything is now in the `moduleName` module ;)
    var _module = a.bind(a, a.module);
    var m = _module(moduleName, []);
    a.module = function () { return m;};
    document.querySelectorAll('[ng-app]')[0].setAttribute('ng-app', moduleName);
})(window.angular, 'moduleNameFromConfig');