Is there a way to not pollute global namespace?

[CreatCodeBuild]

Is it possible to not compile code into global but to an object the user can supply?

I am imagining something like

// xxx.js
// Instead of doing
(function() { // ... GopherJS Code })(this)
// Do
(function() { // ... GopherJS Code })(myObject)

So that the importer/user can do

import myObject from "xxx"

[dmitshur]

How much global namespace pollution is there? The generated JavaScript code is contained in a closure, and this parameter is needed for js.Global to access the right thing.

You can do things like js.Global.Set("foo", ...) to export something from Go code to other JavaScript code, which is described at https://github.com/gopherjs/gopherjs#providing-library-functions-for-use-in-other-javascript-code.

[flimzy]

I've often wished for this, as well. Not becuase pollution is a problem, per se, but because there's no way to know if my global name is used by some other package, so I end up creating global variable names longer than any reasonable person would ever use, just to reduce the chance of collision.

[CreatCodeBuild]

@flimzy Actually that's what I meant by "polluting the global space". Too bad that I haven't get a chance do any GO + JS project for real. So I don't have much input here.