{{ !articles[0].partner.isSponsoringArticle ? "Platinum" : "Portal" }} Partner
architects,high-perf,amd,performance,tips and tricks,node.js

Writing AMD Modules Using amdefine on Node.js

James Burke’s npm module amdefine lets you write AMD modules [1] that also work on Node.js. To do so, you need to perform the following steps:
  • Install amdefine:
        npm install amdefine
    Optional: install into your project by making it a dependency in your package.json.
  • Prefix your AMD with the following line (split into three lines below):
        if (typeof define !== 'function') {
            var define = require('amdefine')(module)
    That line will be removed when packaging your AMDs for deployment via the RequireJS optimizer.
The amdefine readme has more information. Writing an AMD in this manner has one disadvantage: To use it on Node.js, one has to install amdefine. Node’s maintainers want to keep the system small and didn’t want to build AMD support in. However, they might reconsider if demand can be proven, by enough people installing amdefine.

If you don’t want to force Node.js users of your module to install amdefine, there are alternatives [2] for writing AMDs that also work on Node.js. But they have other disadvantages.


  1. The power of the Asynchronous Module Definition
  2. Bridging the module gap between Node.js and browsers

Published at DZone with permission of {{ articles[0].authors[0].realName }}, DZone MVB. (source)

Opinions expressed by DZone contributors are their own.

{{ tag }}, {{tag}},

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}
{{ parent.authors[0].realName || parent.author}}

{{ parent.authors[0].tagline || parent.tagline }}

{{ parent.views }} ViewsClicks