jquery path configuration breaks jquery plugin.

[clmath]

For example this problem appears when you mix code using the dist version of jquery and code using the jquery plugin.

To load the dist version of jQuery with requirejs you need something like:

requirejs.config({
    paths: {
        "jquery": "jquery/dist/jquery.min"
    }
});

Then, if the jquery plugin is used before the dist jquery is loaded, the jquery plugin will try to get the jquery module foo at jquery/dist/jquery.min/src/foo.js (since the jquery globals are not set yet).

I don't see an easy way to solve this. Maybe @wkeese have an idea on this ?

PS: issue encountered by @edchat.

edit: if jquery is loaded before the use of the jquery plugin, it's ok because the globals are set and the plugin returns them.

[wkeese]

I don't even understand what you are doing. If you want to use the "dist version" of jquery you should load it via an explicit <script> tag.

If you want to load jquery through requirejs, then it should be handled like any other package: installed via bower and optionally minified/built into a layer using the ibm-js builder.

Can you give a more complete code example?

[clmath]

If you want to use the "dist version" of jquery you should load it via an explicit <script> tag.

Some user will use requirejs to load the build version of jquery and then load scripts that depends on it.
This is documented in requirejs documentation with sample like this:

requirejs.config({
    shim: {
        'jquery.colorize': {
            deps: ['jquery'],
            exports: 'jQuery.fn.colorize'
        },
        'jquery.scroll': {
            deps: ['jquery'],
            exports: 'jQuery.fn.scroll'
        },
        'backbone.layoutmanager': {
            deps: ['backbone']
            exports: 'Backbone.LayoutManager'
        }
    }
});

In this case, the user don't know which parts of jquery colorize depends on, so he cannot use the jquery plugin and needs to load the whole library at once.

[wkeese]

OK. Well, I'm not sure how you want to fix that. The initial approach for the jquery plugin was to make every app manually do something like

requirejs.config({
    paths: {
        "jquery": "jquery/dist/jquery"
    }
});

The fancy code currently in the jquery plugin (which IIRC internally calls requirejs.config()) is trying to avoid that cumbersome requirement.