jrburke/requirejs — Issue #210: Plugin Paths
Author: amchang
Created: 2012-03-09 23:26:33+00:00
State: open

So I'm running into some issues into using plugin named paths.

Example:

require.config({
paths: {
googleMaps: 'goog!maps,3,other_params:sensor=false'
}
});

If I end up doing require(["googleMaps"]) it appears that requireJS will treat this path as direct url to a script file, instead of being interpreted as a path with a loader plugin.

Is this by design or am I missing something?

I am mostly trying to avoid having to type the goog! plugin constantly in my code, and would rather just use a named path while avoiding defining a global variable or something to store the path.