Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

qunit dropped node 8 without a breaking change

See original GitHub issue

qunit 2.11.0 changed its engines declaration to >=10.

The current stable release (4.6.0) of ember-qunit supports node 8, and depends on qunit ^2.9.3.

Should we do a 4.6.1 release that restricts the qunit range to avoid the breakage?

Issue Analytics

State:
Created 3 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

rwjbluecommented, Jan 14, 2021

😞 I should’ve fixed in 4.x, but didn’t get to it. Sorry folks.

0reactions

Turbo87commented, Dec 20, 2020

@rwjblue is this still relevant or should we close it, now that v5 is out?

Top Results From Across the Web

qunit-dom/CHANGELOG.md at master - GitHub

Changelog. v2.0.0 (2021-08-30). Breaking Change. #1214 Drop support for Node.js 10 (@Turbo87). Documentation. #983 doc(release): remove extra 'to' ...

qunit-dom | Yarn - Package Manager

Fast, reliable, and secure dependency management.

QUnit 2.0 Upgrade Guide

This guide will assist you in upgrading from QUnit 1 to QUnit 2. Overview. The QUnit 2 release only removes old methods. The...

Changelog - Sinon.JS

This is potentially breaking, but should not be, as the breaking change deals with the Node timer object created by fake timers. eba42cc3...

Changelog - Karma test runner

drop node 8, adopt node 12 (#3430) (a673aa8) ... on the fact that Karma uses Bluebird promises may break as Bluebird-specific API is...