This file provides the bootstrap for loading other modules, in particular the require() function, previously known
as dojo.require(). See the loader documentation for further details of how modules are loaded.

For backwards-compatibility, when dojo.js is included without the async:true configuration flag, all the
modules in dojo/_base are implicitly loaded.

The dojo/_base directory contains modules with basic functionality, such as array operations. Typically, if a function
or class exists within the dojo namespace directly (e.g. dojo.forEach()) then it is defined in dojo/_base.

However, note that the modules in dojo/_base are being phased out in favor of top level modules in the dojo/
directory. The dojo/_base files will be maintained until the 2.0 release. See details below for replacement modules.

While using the legacy API, many of the modules listed here are auto-loaded and made available in the global scope for
Legacy compatibility purposes, it is not advisable. The best practice is to require in only the modules you need to use
within your application. For example, previously, if you need to retrieve a DOM node by its ID, you might have
accomplished this by just accessing the dojo global scope object like:

varmyNode=dojo.byId("myNode");

But to ensure the current best practices from Dojo 1.7 onwards, you should do the following:

The following modules define the core DOM API for the Dojo Toolkit. For compatibility purposes, aliases to the Legacy
API are defined in dojo/_base/html and dojo/_base/xhr modules. For new
development it is recommended to require only the individual modules of the parts of the API that are needed and to
reference them via their return variable. See each module for examples of what the common conventions are for doing
this.