Best practice for documenting javascript library dependencies

Viewed 2079

So you're creating a bunch of code in an external .js file that requires jQuery and a few of its plugins, or MooTools, or perhaps some more esoteric libraries. Obviously the actual "include" is done in the host HTML page in the HEAD section as you load in each script.

But as a best practice for portability, what built-in features, or widely-adopted conventions exist within your JavaScript .js file to ensure that the next schmoe who uses your code remembers to also include those other required libraries?

I'm looking for some consensus from the developer community, so please be sure to vote for the answer that seems most common or that you are the most familiar with.

4 Answers
Related