#Plugins#
##Motivation##
We have had several requests to add support for different resource types to basket.js. I propose that rather than add new code paths for each resource type directly to the library, we instead provide the features necessary for consumers to provide their own extensions. This discussion covers the options available to us in providing these features along with any associated risks.
##Extending to other text-based resources##
The current model makes two important assumptions. The first is that the resource that is fetched is a text document. The second is that the resource represents a JavaScript file.