jsonp is undefined (not all the time though) about requirejs-plugins HOT 4 CLOSED

it is indeed a bug... if 2 requests happen at the same time they will point to wrong callback (since I'm using new Date to generate the callback ID).. thanks for reporting it, I wouldn't notice it since I only use the async to load gmaps and it only happen once...

"callback" is the default parameter passed to the script so async!http://twitter.com/statuses/user_timeline/Integralist.json have the same effect as async!http://twitter.com/statuses/user_timeline/Integralist.json!callback (both request the URL "http://twitter.com/statuses/user_timeline/Integralist.json?callback=_global_callback_method_"

you can load JSONP data by simply passing define as a the callback (same effect as using the async plugin):

require(['http://twitter.com/statuses/user_timeline/Integralist.json?callback=define'], function(data){
  console.log('feed: ', feed);
});

from requirejs-plugins.

That last example doesn't work for me...

require(['http://twitter.com/statuses/user_timeline/Integralist.json?callback=define'], function(feed) {
    console.log('feed: ', feed);
});

...I just get the error: Uncaught TypeError: Object #<Object> has no method 'indexOf'

from requirejs-plugins.

ahhhh according to RequireJS documentation:

Only JSONP return values that are JSON objects are supported. A JSONP response that is an array, a string or a number will not work.

twitter returns an Array, so the async! plugin is indeed needed.. - I forgot why I was using the async plugin for JSONP on all my projects :P #irony

I will fix it right now, just updating the example page with more info.

from requirejs-plugins.

All good! Just tested and it's working as expected :-)

from requirejs-plugins.