Check the module object itself for accessing module.exports

[mttwc]

On some sites, the exports variable is being used for other (non-node) things, resulting in the wrong code path being executed, leading to Uncaught ReferenceError: module is not defined(…). This PR adds an additional check for the module object itself before trying to access it.

Fixes #318

[rodneyrehm]

Thank you!

Is there a reason to not go with typeof module === 'object' && module.exports instead, as umd/returnExports.js shows? I mean other than the original code testing for typeof exports === 'object' and this fix being the smallest possible change?

[mttwc]

Not that I can think of, good call :)
I'll amend it now!

[larsendaniel]

👍

[rodneyrehm]

Thank you!
Your fix has been released as v1.18.3

[mttwc]

Excellent! Thanks for being so quick on this!