cujojs/wire — Issue #16: Investigate better AMD domReady options
Author: briancavalier
Created: 2012-01-26 17:18:20+00:00
State: open

See the discussion in #15 about some of the pros and cons of relying on the AMD loader's `domReady!` plugin, versus a `domReady` module (if it provides one). Here's a summary:

1. `domReady!` plugin can cause module loading to fail if DOMReady doesn't fire before the AMD loaders failure timeout (specifically, RequireJS, not sure if other loaders have an explicit failure timeout). Using `domReady` as a module doesn't have this problem.

1. `domReady` module requires an AMD loader path config in every loader I've tried, unless you move it directly into baseUrl. Some loaders (e.g. curl) can automatically locate their `domReady!` plugin without additional configuration.

So, we need to figure out which is best for `wire/domReady`