Given the above configuration, we can now access /jquery/[VERSION/]METHOD_NAME in our browser. JSAPI.info will only source the jQuery source file remotely (from googleapis) if it hasn't already cached it locally.

How does it work?

It works by loading the library you specify into an instance of jsdom, and then evaluating the method you specify (in fully qualified form, e.g. jQuery.fn.css) within that instance. It then matches the toString() representation of that function (thanks V8!!) against the source of the library, thus determining its location. It's all operating under node.js, running via a beautiful configuration of nginx (primed to microcache!) on a linode box somewhere in London.

Installation / Running it

cd jsapi-info/app

npm install .

node server 8001

Server should be running on :8001

Changelog

1.0.0 - Gotta start somewhere

1.1.0 - Add package.json to manage dependencies. Linkifies this.methodName calls with new LINK_MARKER syntax (incl. name of item, e.g. this.css, and the full name, e.g. jQuery.fn.css). Sorts methods in sidebar by similarity to current method name (done with similarity.js).

1.1.1 - Fixed ?expand option so it doesn't go beyond the end of the source file. Fixed issue where names present in global scope, even if not functions, take precedence in resolver, e.g. window.outerHeight when querying /jquery/outerHeight. Fixed this by including a typeof v == 'function' check in the embedded resolver function. Also fixed error being thrown when a method can't be found.

1.1.2 - Added jQueryUI to libs and added a require option in the JSON config (currently only used with jQuery UI). Also generalised SHLoader.