Core: Migrate from AMD to ES modules 🎉

Migrate all source AMD modules to ECMAScript modules. The final bundle
is compiled by a custom build process that uses Rollup under the hood.

Test files themselves are still loaded via RequireJS as that has to work in
IE 11.

Tests can now be run in "Load as modules" mode which replaces the previous
"Load with AMD" option. That option of running tests doesn't work in IE
and Edge as it requires support for dynamic imports.

Some of the changes required by the migration:
* check `typeof` of `noGlobal` instead of using the variable directly
  as it's not available when modules are used
* change the nonce module to be an object as ECMASscript module exports
  are immutable
* remove some unused exports
* import `./core/parseHTML.js` directly in `jquery.js` so that it's not
  being cut out when the `ajax` module is excluded in a custom compilation

Closes gh-4541

1 files changed, 3 insertions, 3 deletions

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 18c6bc802..2deb7d180 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -129,14 +129,14 @@ Rather than rebuilding jQuery with `grunt` every time you make a change, you can
 $ grunt watch
 ```
 
-Alternatively, you can **load tests in AMD** to avoid the need for rebuilding altogether.
+Alternatively, you can **load tests as ECMAScript modules** to avoid the need for rebuilding altogether.
 
-Click "Load with AMD" after loading the test page.
+Click "Load as modules" after loading the test page.
 
 
 ### Repo organization
 
-The jQuery source is organized with AMD modules and then concatenated and compiled at build time.
+The jQuery source is organized with ECMAScript modules and then compiled into one file at build time.
 
 jQuery also contains some special modules we call "var modules", which are placed in folders named "var". At build time, these small modules are compiled to simple var statements. This makes it easy for us to share variables across modules. Browse the "src" folder for examples.