Doing this as a gist, because I don't have time for a polished post, I apologize:
If you had to define an optimal module system that had to work with async, networked file IO (the browser) what would that look like? It would not be node's system, for the following reasons:
- the
require('')
in node is very imperative. It can be called at any time and mean a module should be synchronously loaded and evaluated when it is encountered. How would this work if this call is encountered in the browser case:require(someVariable + '/other')
? How would you know what module to include in any bundle? For those cases, you should allow for an async require to fetch, and leave dependencies that can be bundled to therequire('StringLiteral')
format. Node has no allowance for this, and browserify will not do a good job with those types of dependencies. It will need hints, or explicit out-of-module listing of what to include.
Once you have an MVC system in the browser, it will be common to delay loading of a view and its controller until it is needed, and rely on routing via URLs or button actions to know what module to imperatively ask for next. This works well in AMD since it has a callback-style require for this. This really helps performance: the fastest JS is the JS you do not load. This is a very common practice in use with AMD systems. browserify cannot support it natively. The suggestion when using browserify is to choose your own browser script loader and figure out the loading yourself.
- Similarly, since there is no synchronous module fetching and execution in the browser (at least it would be madness to want to do that), you cannot reliably preload a modifier to the module system so that it takes effect for the rest of the module loading. Example in node is requiring coffeescript in your top level app so that any .cs files are considered in module loading.
Instead, AMD has loader plugins that allow you to specify the type of resource that is being requested. This is much more robust, and leads to better, explicit statements of dependencies. Plus, loader plugins can participate in builds. This is better than the browserify plugins for this type of thing because of the imperative nature of JS code: fs.readFile(someVariable + 'something.txt')
.
Static declaration of dependencies is better for builds. So if you like builds, favor a system that enforces static declaration, and has an async form for non-declarative module uses. ES modules will go this route, and explicitly not use node's module system because of this imperative dependency issue that node has.
The parts that are ugly about AMD:
- It explicitly asks for a function wrapper. Node actually adds one underneath the covers when it loads modules. browserify does too when it combines modules. While it would be nice to not have the function wrapper in source form, it has these advantages:
a) Using code across domains is much easier: no need to set up CORS or restrict usage to CORS enabled browsers. You would be amazed by how many people would have trouble with this as it is a hidden, secondary requirment. So, they are developing just fine on their local box, do a production deployment, then things don't work. This is confusing and not obvious as to why it fails. You may be fine with knowing what to do for this, but the general population still has trouble with this.
b) Avoids the need to use eval(). Eval support in the browser is uneven traditionally (scope differences), and now with CSP makes it even more of a hazard to use. I know there has been at least once case of a "smart" proxies that would try to "protect" a user by stripping out eval statements in JS.
In short, the function wrapper is not the ideal, but it avoids hard to trace secondary errors, and it really is not that much more typing. Use the sugar form if you want something that looks like commonjs/node.
- Possibility for configuration blocks: front end developers have much more varied expectations on project layout. Node users do not. This is not the fault of requirejs or other AMD loaders though. At the very least, supporting a configuration block allows more people to participate in the benefits of modular code.
However, there is a convention in AMD loaders of baseUrl + module ID + '.js'
. If a package manager lays out code like this, then there is no config block needed in an AMD loader. volo does this.
npm could even do this to bridge the gap: when installing a package called dep
, put it at node_modules/dep
and create a node_modules/dep.js
that just requires dep
's main module. That would also then work for AMD loaders (if the modules installed were AMD compatible or converted) if the baseUrl was set to node_modules
.
So, it is entirely possibly to stick with the AMD convention and avoid config blocks. Package manager tools have not caught up yet though. Note that this is not the fault of the core AMD module system. This is a package manager issue. And frankly, package managers have been more focused on layouts that make it easy for them vs. what is best for the runtime use and that avoid user configuration. This is the wrong decision to make. Making it easier for users and runtimes does not actually make it that much more complicated for the package manager.
On package managers:
It is important to separate what a package manager provides and what the runtime module system provides. For example, it is possible to distribute AMD-based code in npm. amdefine can help use that code in a node environment. Particularly if the dep.js
style of file is written out in the node_modules directory.
I would suggest that npm only be used for node-based code though, to reduce confusion on what can be used where. Particularly given the weaknesses of node's module system for browser use. However, some people like to distribute code targeted for the browser in node because they like npm. So be it.
But also note that a strength for node-based npm use, nested node_modules for package-specific conflicting dependencies, is actually a weakness for browser use: while disk space is cheap for node uses, delivering duplicate versions of code in the browser is really wasteful. Also, there is not a need for compiled C code dependencies in the browser case. So some of npm's capabilities around that are unneccessary.
It would be better to use a different type of package manager for front end code that tried to reuse existing module versions installed, possibly warn the user of diffs, but if really needed, then write out an AMD map config in the case that it is really needed.
In closing:
My biggest complaint is that node explicitly ignored browser concerns when designing itself and choosing its module system, but then some people want to use those design decisions and force them on browser use of modules, where they are not optimal. Just as node did not want to compromise to meet existing browser uses of JS, I do not want to use a less-capable module system in the browser.
I am hopeful that ES modules will have enough plumbing to avoid the function wrapper of AMD. But be aware that ES semantics will much more like AMD's than node's. And the ES module loader API will be robust enough to support config options and AMD loader plugins.
But note: this is not to say that someone cannot use node modules with npm and browserify to make something useful that runs in the browser. Far from it. But it will be restricted to the constraints above. There are still wonderful things that fit in that box, so more power to them for constraining themselves to that box and still shipping something useful. There is just more to browser-based module usage though. And I do not want their unwillingness to address that wider world as a reason to accept less for myself. The good news is that the internet is big enough for both sets of users. So let's all hug and move on to just making things.
(note this is a gist, so I am not notified of comments. I may delete this at some point if I get around to doing something more polished for a blog post, or just do not want to see its rough form any more)
You misunderstand what node's module is and when it was formed.
The earliest versions of node took their module system directly from CommonJS. Yes, CommonJS was created outside the constraints of the browser primarily by the developers of Narwhal.
Even during the earliest days of npm @isaacs was working with @ry to tweak the module system. In fact, the way @isaacs ended up becoming one of the earliest "committers" was by taking over responsibility for node's module system and by late 2010 npm and the module system were being developed in tandem.
Browserify 0.0.1 has a version target of 0.2 which means it was created before the module system truly became "node's". @substack was also involved in the changes in the module system, mostly re-actively since most changes rippled through browserify.
Most of the complaints I see here, especially those relating to versioning and localization of deps are all decisions made long after browserify was created and are unique to node and in some cases even cause spec incompatibilities with CommonJS. In fact, without browserify I think some things may have been very different but browserify was showing that browser packages could be built from node's module system without changes.
So yes, the browser was considered. Remember that during this time @isaacs and I were still in CommonJS while they went down the AMD rabbit hole and the first version of the npm registry was even described as a standard for CommonJS around the same time people were arguing about which AMD spec to go with.
Node's module was free not to ignore the browser or to focus on being a systems module system, Node's module system was free to focus on being the best module system for modules.
That is why it has succeeded, the first and most important customer of a module is modules and node continues to be the easiest way to write, publish, and consume modules. Every other consideration is secondary.
I have a lot more graphs now, and a lot more data :) I've been ripping data out of GitHub for a while and it says a lot more than just the module counts do.
The first thing it shows is that there really isn't a node ecosystem and a browser ecosystem. A huge portion of the engagement is in browser tools and modules and the people stretch between between different parts of the ecosystem.
Once you realize that node, on a community level, is not separate from the web but that it is of the web and has become a vertebra in the spine of web development these arguments become very very moot.
What is the best module system is subjective, node's is the fastest growing, not just in comparison to other JS module systems but in comparison to all module systems. Adoption matters.
We aren't fighting for what system people use to package modules in to their apps, and RequireJS certainly has more features to offer here than browserify, we're fighting for how people define their modules. In that, node's module system is winning, and all browser tools would benefit from adopting support for modules built in it. For its part browserify will consume a module written to any modern standard.