Remove support for delaying qunit.js via AMD

The current check in bridge.js is problematic because if a project
includes RequireJS anywhere, for any purpose, the bridge crashes
unless RequireJS is also in charge of loading QUnit.

QUnit 3.0 will remove support for its built-in AMD export
(ref qunitjs/qunit#1729).

It remains supported to use AMD/RequireJS in your HTML file, and to
use it to load source code and/or test files. However, it is no
longer supported to delay the loading of qunit.js itself via AMD.

In order to make that use possible in QUnit 3.0, the bridge.js must
stop assuming that presence of define.amd implies using it to load
QUnit itself.

Example at https://qunitjs.com/api/config/autostart/#loading-with-requirejs

Author: Krinkle

chrome/bridge.js

@@ -7,18 +7,13 @@
  */
 
 /* global QUnit:true */
-(function (factory) {
+(function() {
+  'use strict';
+
   if (window.self !== window.top) {
     // Ignore iframes. https://github.com/gruntjs/grunt-contrib-qunit/issues/202
     return;
   }
-  if (typeof define === 'function' && define.amd) {
-    require(['qunit'], factory);
-  } else {
-    factory(QUnit);
-  }
-}(function(QUnit) {
-  'use strict';
 
   var lastMessage = performance.now();
 
@@ -137,4 +132,4 @@
   QUnit.done(function() {
     sendMessage('qunit.done');
   });
-}));
+}());

docs/qunit-examples.md

@@ -94,9 +94,6 @@ grunt.initConfig({
 });
 ```
 
-## Loading QUnit with AMD
-When using AMD to load QUnit and your tests, make sure to have a path for the `qunit` module defined.
-
 ## Events and reporting
 QUnit events are forwarded to Grunt's event system, enabling you to build custom reporting tools. Please refer to the QUnit API documentation on [QUnit events](https://qunitjs.com/api/callbacks/QUnit.on/) and [QUnit callbacks](https://qunitjs.com/api/callbacks/) for when and what data is exposed from these events.