requirejs-define

I have legacy code and a module definition like this: define(["a", "b", "c", "d"], function(a, b, c) { ... }); You can see that there are more dependencies than actual params that we are using at module. Does it make any sense? I think module "d" is redundant. This only means that module "d" (or, to be more precise, the result of calling "d"'s factory function) won't be passed as a parameter (e.g. d ) to the function, so it won't be available inside it. It's possible that module "d" executes some code with side-effects so removing it could potentially change how you application behaves (i.e.

I have searched high and low for documentation on this, but I just cannot find anything anywhere. I am using Aloha and want to use their sidebar prototype to create a new side bar of my own attached to other plugin functionality. Their sidebar.js starts off with this, but I can't for the life of me find any documentation that explains what it means. define( [ 'aloha/core', 'aloha/jquery', 'aloha/selection' ], function (Aloha, jQuery, Selection, Plugin) { It then goes on in that wrapper to define a bunch of functions, so vars and some proptotypes - which I can just about get my head around...