Regression of #163, automatic use of empty: for CDN URLs

[jwhitley]

A user of requirejs-rails has noted what appears to be a regression of a change introduced in #163, to automatically treat URLs as empty: in build configs. See jwhitley/requirejs-rails#87 for details. Let me know if I can be of any help in reproducing, etc.

[jrburke]

Asked for more info in the original ticket, not clear yet to me what is going wrong.

[pboling]

This is a problem for me. CDN assets are not working with require JS. Particularly following the Facebook instructions for using the JDK with Require:
http://developers.facebook.com/docs/javascript/howto/requirejs/

[jrburke]

@pboling do you have a sample or test I can try? Preferably something where I do not have to run requirejs-rails as I do not have that set up.

Perhaps if you could pass me a simple module that uses the facebook sdk, the runtime requirejs.config you use in the browser, then the build config that is passed to r.js I could try to reproduce a test case using just r.js directly.

[pboling]

I'll work on getting a simple example setup, assuming I am able to reproduce the issue outside of requirejs-rails.

[pboling]

My problem seems to be a result of using almond to build my main.js, and almond not supporting CDN/external files.

[jrburke]

OK, yes, you can just build with require.js in that case instead of almond. You will need to set up a paths config though, and call the library something other than 'require', since 'require' is a reserved dependency name. Calling it anything else is fine, see second code snippet here for an example:

http://requirejs.org/docs/optimization.html#onejs