r.js 1.0.3 always passes truthy to uglify for strict_semicolons option

[ArturDorochowicz]

Changes in #67 (7650beb#L1L265) introduced an issue where a truthy value (config object) is always passed to uglify.js for strict_semicolons option. This makes it impossible to control that option and is too strict - the default value is false.

[busticated]

+1

After a fair amount of time digging into why my known-good projects were all now throwing "Cannot uglify file... Unexpected token" errors, it seems this is the root cause.

[jrburke]

Thanks for finding this. I'll work on doing a 1.0.4 release in the next few days to get this fixed.

[busticated]

thanks James!

[jrburke]

This is fixed now in r-edge.js if you want to try the fix, and it will be part of a 1.0.4 release that goes out this week. Sorry I let this one go so long without a fix. I just goofed the original change in #67 when I was translating/checking the API calls on the uglifyjs site.