Conflict caused by the "exports" object

[rkyoku]

Hi,

The "exports" object created by RetinaJS is causing a conflict with a third party UMD bundler, used (among others) by Tooltipster.

The UMD loader checks the existence of "exports", and asserts that if it exists, we are in a Node environment. Which is not the case.

Is it possible for RetinaJS not to create this variable?

[bartvollebregt]

I think I'm having the same issue while using an external plugin.
I'm using the bootstrap datetimepicker: https://eonasdan.github.io/bootstrap-datetimepicker/

It throws a module.exports not defined error which is probaply related to this.

[rounders]

Also causes an issue when using Handlebars (http://handlebarsjs.com). Because of the existence of the 'exports' object, Handlebars doesn't load properly. Looks like same reason as above, handlebars looks for existence of "exports" object and if it finds it, it assumes we are in a Node environment.

[nkals722]

FWIW, the issue seems to only effect the minified version. Also, if you do a search and replace for "exports" and change it to something like "retexports", then the minified version works again. Would be nice to have an official version with that fix released though.