If you thought that the only methods to include jQuery were via a manual download or using a CDN link, then hopefully this chapter has opened your eyes to some alternatives—let's take a moment to recap what we have learned.

We kicked off with a customary look at how most developers are likely to include jQuery before quickly moving on to look at other sources.

We started with a look at how to use Node, before turning our attention to using the Bower package manager. Next, we had a look at how we can reference individual modules within jQuery using the AMD approach. We then moved on and turned our attention to creating custom builds of the library using Git. We then covered how we can use source maps to debug our code, with a look at enabling support for them within Google's Chrome browser.

To round out our journey of loading jQuery, we saw what might happen if we can't load jQuery at all and how we can get around this, by using Modernizr to allow our pages to degrade gracefully. We then finished the chapter with some of the best practices that we can follow when referencing jQuery.

In the next chapter, we'll kick things into a gear by taking a look at how we can customize jQuery. This can be done by replacing or modifying a function or applying a patch during runtime; are you ready to get stuck in?