Click here to Skip to main content
Click here to Skip to main content
Technical Blog

#javascript Require.js vs CommonJS / AMD modules and #angularjs

, 17 Mar 2014 CPOL
Rate this:
Please Sign up or sign in to vote.
#javascript Require.js vs CommonJS / AMD modules and #angularjs

I recently replied to the following twitter conversation about require.js vs browserify.


Angular.js and AMD

Recently, I tried to integrate some AMD modules into an angularjs application. I did not spent much time on it but I was under the impression that the integration was not straightforward.

On this twitter thread, @tbranyen pointed to me that using the angular dependency injection annotations, I can easily reuse my existing require.js modules. I must give it a try on my next project.

AMD vs CommonJS

First of all, I must say that I can understand the arguments from the CommonJS supporters, but the require.js configuration file gives me extra powers...

An awesome feature of requirejs is that you can create different execution context. This means that you can, for instance, load different versions of the same module into two different context executions. This can be very powerful.

I'm using this on my js-utils project to make it just a repository of modules without hard dependencies. This means that js-utils node_modules folder will have just a few references.

var requirejs = require('requirejs');

requirejs = requirejs.config({

    /// isolate this context
    context: 'context1',

    /// use local packages, located on node_modules
    nodeRequire: require,

    /// modules baseurl
    baseUrl: __dirname,

    /// the lookup paths
    paths: [ ... ]

});

I do not consider myself a fanboy of require.js because:

  • I know that its complexity demands a bigger learning curve that it's not always required.
  • I know that browserify is more easy and compatible with node modules.
  • I know that its syntax can be very verbose.
  • I know that r.js needs a lot of improvements.
  • I know that r.js source maps are almost useless (the variables and functions are already minified).

But I also know that:

  • I can create complex dependencies on require.js config file
  • I can create friendly alias on require.js config file
  • I can easily change version of the dependencies just by changing the configuration file
  • I can use different execution contexts

If I said anything wrong, please let me know because I really want to hear your thoughts on this matter!

@aetheon

Visit www.divhide.com for more information, contacts and news about Web Development.
See other blog posts at blog.divhide.com.

Divhide purpose is to follow the HTML5 movement and contribute with applications which prove the quality of technology.
Feel free to contact divhide.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

aetheon
Web Developer
Portugal Portugal
No Biography provided

Comments and Discussions

 
QuestionJS Including Engine PinmemberAlexandru Lungu24-Mar-14 3:50 
QuestionRequireJS / AngularJS PinmemberKenneth Kasajian18-Mar-14 17:27 
AnswerRe: RequireJS / AngularJS Pinmemberaetheon18-Mar-14 23:38 
GeneralRe: RequireJS / AngularJS PinmemberKenneth Kasajian19-Mar-14 16:40 
GeneralRe: RequireJS / AngularJS Pinmemberaetheon19-Mar-14 23:12 
GeneralRe: RequireJS / AngularJS PinmemberKenneth Kasajian27-May-14 12:07 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web04 | 2.8.141223.1 | Last Updated 17 Mar 2014
Article Copyright 2014 by aetheon
Everything else Copyright © CodeProject, 1999-2014
Layout: fixed | fluid