Avoiding polluting the global namespace with javascript dependencies

Question

I'm building a javascript library and would like to bake in various dependencies (e.g, jQuery, Google Closure, etc) without polluting the global namespace. This is particularly important because others may already be using different versions of these libraries.

As far as I can tell most of these libraries attach themselves directly to the window object, so I cannot simply put them in an anonymous function.

Are there any general solutions to this problem?

typeof · Accepted Answer · 2011-03-23 21:47:16Z

2

I believe you would need to modify the library source code to be able to do this, replacing their code:

window.jQuery = function(){ ... }

with:

myNamespace.jQuery = function() { ... }

Any any reference to the global jQuery object (and alias) would have to be namespaced, too. Similar measures would have to be taken for each JS library.

In my opinion, this is too much trouble for what it's worth. Taking up a single global variable for each js library is acceptable.

answered Mar 23, 2011 at 21:47

typeof

5,9722 gold badges18 silver badges19 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Avoiding polluting the global namespace with javascript dependencies

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related