Release build leaks into global scope about javascript.util HOT 1 CLOSED

Q: With scope leak, do you mean the first group of statements in javascript.util.js?

A: No javascript.util.js is another issue and I think it's the right way to do it i.e putting "javascript" in global scope is ok and compatible with the old lib. It also hides the browserify stuff from the lib user completely.

The global scope leakage is from the browserify code added to the built lib. "require" and "process" is leaked (and more?). I guess this is intentional by browserify to make CommonJS API available in the browser. I'd like to keep that completely hidden though, perhaps by simply enclosing the built lib with a private scope. This also means we should browserify javascript.util and jsts togheter when jsts is ready so that browserify stuff is only included once.

from javascript.util.