Uncaught ReferenceError: global is not defined

[nikku]

It is not save to rely on global being available in browserified bundles (i.e. users may choose to disable insertion of global variables to keep the bundle minimal.

In case browserify (or webpack) did not expose a global variable support.js throws an error saying

Uncaught ReferenceError: global is not defined

I am not sure what the right approach would be to solve this issue. I would probably check for window as a global variable because that should (?) always be available in DOM environments.

[nikku]

global is the conventional root in commonJS thought. It may be safe to assume users do not exclude it unless they know what they are doing.

[jdalton]

global is the conventional root in commonJS thought. It may be safe to assume users do not exclude it unless they know what they are doing.

Right and the lodash-node bundle is a build of lodash explicitly exported as Node.js/io.js modules.

[nikku]

Is there any npm compatible build of of lodash that is compatible with the browser + browserify then?

[jdalton]

There's lodash and lodash-compat though they only have UMD in the monolithic index.js files and not the other modules included. Browserify has opts.detectGlobals as true by default so things should work. Others have used Browserify with lodash without problems so I think this is a case of using the right Browserify options for the job.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.