jquery/test/karma.debug.html
Michał Gołębiowski-Owczarek 5701957b72
Build: Drop individual AMD modules
With this change, jQuery build no longer generates the `amd` directory with
AMD modules transpiled from source `src` ECMAScript Modules. To use individual
jQuery modules from source, ESM is now required.

Note that this DOES NOT affect the main `"jquery"` AMD module defined by built
jQuery files; those remain supported.

Closes gh-5276
2023-06-27 18:23:58 +02:00

46 lines
1.4 KiB
HTML

<!DOCTYPE html>
<html lang="en" id="html">
<head>
%X_UA_COMPATIBLE%
<title>DEBUG</title>
<meta charset="utf-8">
<!-- Karma serves this page from /context.html. Other files are served from /base -->
<link rel="stylesheet" href="/base/external/qunit/qunit.css" />
<link rel="stylesheet" href="/base/test/data/testsuite.css" />
</head>
<body id="body">
<div id="qunit"></div>
<!-- Start: jQuery Test HTML -->
<!-- this iframe is outside the #qunit-fixture so it won't waste time by constantly reloading; the tests are "safe" and clean up after themselves -->
<iframe id="loadediframe" name="loadediframe" style="display:none;" src="/base/test/data/iframe.html"></iframe>
<div id="qunit-fixture"></div>
<!-- End: jQuery Test HTML -->
<!-- Start: Karma boilerplate -->
<script src="/context.js"></script>
<script src="/debug.js"></script>
<script>
%CLIENT_CONFIG%
%MAPPINGS%
</script>
%SCRIPTS%
<!-- End: Karma boilerplate -->
<script src="/base/test/data/qunit-fixture.js"></script>
<script>
// QUnit.config is populated from QUnit.urlParams but only at the beginning
// of the test run. We need to read both.
var esmodules = QUnit.config.esmodules || QUnit.urlParams.esmodules;
// Workaround: Remove call to `window.__karma__.loaded()`
// in favor of calling `window.__karma__.start()` from `loadTests()`
// because tests such as unit/ready.js should run after document ready.
if ( !esmodules ) {
loadTests();
}
</script>
</body>
</html>