Adds a yui module name into the core YUI configuration which is used by loader to identify the pieces that are already part of the seed and should be attached to Y automatically.

Set a custom loader configuration for the group.

Here is an example of how to use it.

app.yui.applyGroupConfig('app', {
    maxURLLength: 2048,
    comboBase: "/combo?"
    comboSep: "&"
});

Build a list of urls to load a list of css modules.

var links = app.yui.buildCSSUrls('cssbase', 'cssflickr@hermes');

As a result, links will be an array with the urls that you can use in your templates to provision styles.

Modules as cssflickr@hermes denotate a module from a particular group, as in <module-name>@<group-name>. Modules without the group denotation will be assumed as core modules from yui.

Build a list of urls to load a list of modules.

var scripts = app.yui.buildJSUrls('node', 'photos@hermes');

As a result, scripts will be an array with one or more urls that you can use in your templates to insert script tags.

Modules as photos@hermes denotate a module from a particular group, as in <module-name>@<group-name>. Modules without the group denotation will be assumed as core modules from yui.

Build the list of urls to load the seed files for the app.

var scripts = app.yui.getSeedUrls();

As a result, scripts will be an array with one or more urls that you can use in your templates to provision YUI. Keep in mind that if use expressYUI.expose() middleware, you don't need to provision the seed, it will be provisioned automatically as part of the state object.

Waits for the app to be ready, including the YUI instance to notify back that the ready state of the app was reached by calling the callback. The ready state is bound to the locator instance mounted into the express app thru app.set('locator', locator); and depending on app.get('locator').ready.then() promise result, the ready state will be reached or not.

app.yui.ready(function (err) {
    if (err) {
        throw err;
    }
    // do something!
});

Create a synthetic group off the bundle renference to register its modules into the server and/or client Y instance so they can be used thru app.yui.use().

Register a group by defining the group configuration for the loader. Groups can be served from origin app or from CDN by calling applyGroupConfig or by setting yui default base, yui default root and yui combo config thru app.set().

Here is an example on how to use it, assuming that the YUI metadata are located in the build directory under the app root.

app.yui.registerGroup('app', __dirname + '/build', 'loader-app');

Creates a YUI Instance, and wraps the call to Y.require() to work appropiatly on the server side. The require method can be called once the ready state is achieved thru app.yui.ready().

app.yui.ready(function (err) {
    if (err) {
        throw err;
    }
    app.yui.require('json-stringify', function (Y, imports) {
        Y.JSON.stringify({ entry: 'value' });
    });
});

Specify a list of modules to use as seed. This method extends the yui static configuration, specifically setting the app.yui.config().seed value.

app.yui.seed(["yui-base", "loader"]);

Set YUI Core Modules from the same origin as to where the application is hosted.

This is not recommended for production and instead you should use a cdn to server the build folder, but it is a very useful feature for development. Here is an example on how to use it:

app.yui.setCoreFromAppOrigin();

Creates a YUI Instance, and wraps the call to Y.use() to work appropiatly on the server side. The use method can be called once the ready state is achieved thru app.yui.ready().

app.yui.ready(function (err) {
    if (err) {
        throw err;
    }
    app.yui.use('json-stringify', function (Y) {
        Y.JSON.stringify({ entry: 'value' });
    });
});