-
Notifications
You must be signed in to change notification settings - Fork 778
Write the QUnit 3.0 Upgrade Guide #1808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Krinkle
added a commit
that referenced
this issue
Apr 10, 2025
* Describe benefits of test.each(). * Use simpler and more practical test.each() examples. * Add a standalone example of how assert.rejects() is used in practice, separate from the longer demonstration of each possible matcher. Ref #1808.
Krinkle
added a commit
that referenced
this issue
Apr 10, 2025
Krinkle
added a commit
that referenced
this issue
Apr 10, 2025
* Describe benefits of test.each(). * Use simpler and more practical test.each() examples. * Add a standalone example of how assert.rejects() is used in practice, separate from the longer demonstration of each possible matcher. Ref #1808.
Krinkle
added a commit
that referenced
this issue
Apr 10, 2025
Krinkle
added a commit
that referenced
this issue
Apr 10, 2025
* QUnit 2.x and QUnit 3.0 have the same browser support. * QUnit 3.0 removes support for PhantomJS and raises the Node.js requirement. * The new "ESM" bundle for QUnit 3.0 has a higher browser requirement because ESM itself (i.e. `<script type=module>` and the `import` keyword) did not exist in browsers before that. Since commit ec7d6e7 the new ESM build uses a higher Rollup/Babel target that leverages native use of ES6 syntax instead of compiling to ES5. Ref #1808.
Krinkle
added a commit
that referenced
this issue
Apr 10, 2025
* QUnit 2.x and QUnit 3.0 have the same browser support. * QUnit 3.0 removes support for PhantomJS and raises the Node.js requirement. * The new "ESM" bundle for QUnit 3.0 has a higher browser requirement because ESM itself (i.e. `<script type=module>` and the `import` keyword) did not exist in browsers before that. Since commit ec7d6e7 the new ESM build uses a higher Rollup/Babel target that leverages native use of ES6 syntax instead of compiling to ES5. Ref #1808.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ref #1498
Ref https://github.com/qunitjs/qunit/blob/3.0.0-alpha.4/History.md
The text was updated successfully, but these errors were encountered: