`require`, `exports`, and `module` are treated as external modules about curl

RequireJS exhibits no issues with the define(['exports'], function(exports){ ... }) pattern, but perhaps I'm using it incorrectly.

[unscriptable]

Hey Kit!

You're using it correctly. Btw, that's some awesomely comprehensive boilerplate in your example. :)

This appears to be a google closure issue. My tests fail in the same way when I use the closure-compressed curl.js files in the dist folder. If you want to move forward, use the uncompressed curl.js in the src folder while I look into this further.

Thanks for finding this!

• John

Hi John!

I just tested it with the uncompressed curl.js, and it works perfectly. Thanks so much for looking into this; I thought that my call to define may have been in error. I'm using curl.js in a unit test to ensure that my library is compatible with AMD script loaders, so minification is not a concern.

If you'd like, however, I can test minification with Uglify for you...I've found that it produces better results than Closure Compiler in some cases.

Thanks again!

[unscriptable]

Found the problem. I needed to quote some commonjs parameter names ("exports", "require") in some more places. unscriptable@7b26633

[unscriptable]

The fix for this was committed in unscriptable@7b26633. Closing.

Fantastic!