Gourmet vs Qoopido.demand

Auto-asset inclusion, native CSS support, and flexible bundling make handling your assets simple.

Supports ES6 syntax by default.

Declarative configuration makes project setup easy.

The runtime environment allows for isomorphic rendering of React applications by default.

Modules will get loaded via XHR/XDR and get cached in localStorage to prevent further requests which improves performance escpecially on mobile

Any type of dependency can have multiple URLs defined to be used as fallback.

Loading is dealt with via handlers that are themselves modules (dynamically loaded and cached). Qoopido.demand comes with support for its own module format built-in and offers handlers for css, json and text. Due to handlersbeing modules themselves it is really easy to write custom handlers.

Support for SHA256, 384 and 512 identity checks for all types of loaded modules was added in version 2.0.7

By taking advantage of auto-bundling, it means that demand itself will combine requests without the user having to manually define a bundle.

Cached modules can be optionally & automatically compressed with lz-string loading a plugin (included in the distribution) either globally or on a per module or even per path/part of path base.

Version 1.1.2 of Qoopido.demand adds the possibility to not only set global caching parameters valid for all modules but allows for fine grained cache control on a per module basis.

It's the one of the few modules in this category that can handle IOC-style dependency injection. The others work well for apps that have knowable dependency lists at compile time, but this is one of the few that can load new modules without being recompiled.

Cookie support within Qoopido.demand can be enabled globally or per module. Whenever the localStorage cache for a module changes an accompanying cookie gets updated/deleted so the server can handle the clients module caching state and, e.g., inline modules as long as the client das not have them in localStorage.

Qoopido.demand offers loading of legacy scripts as if they were modules through probe functions. These probe functions are similiar to Require.js shim, but where shim allows only string parameters, Qoopido.demand's probes are JavaScript functions that can check whatever you want.

Although not depending on native promise support it offers a promise like interface which greatly improves readability of code

Dynamically loaded modules can have further dependencies that will get dynamically resolved and loaded

It enables and encourages the development of atomic modules that do not necessarily have to get bundled (manually or via build-process) to gain performance

Qoopido.demand has recently added support for legacy browsers. Including IE8.

From version 1.1.1 onwards Qoopido.demand is able to load multiple concatenated modules in a single request (like jsdelivr) while maintaining automatic module resolution.