|
Repo Added
|
Files
37
|
Badge
README BADGES
|
push
github
Build: Update puppeteer and enable allowScripts to fix Node 26 build == Problem 1 == Follows-up 52a999214c. Adding Node 26 to the matrix passed at https://github.com/qunitjs/qunit/actions/runs/36519183067/job/109248101306 .. which was on a branch where we happen to get a lucky cache hit: > Cache hit for: > Linux-<a class=hub.com/qunitjs/qunit/commit/0954bc9ce1cd42bd80bacb333df74f2e5c96b95d">0954bc9ce72a08fed99ac934a417781bc Then the same SHA1 was pushed to master, where it fails: https://github.com/qunitjs/qunit/actions/runs/36519530591/job/109249132879 > Cache not found for input keys: > Linux-0954bc9ce1cd42bd80bacb333df74f2e5c96b95d72a08fed99ac934a417781bc > > npm warn install-scripts 1 package has install scripts not yet covered by allowScripts: > npm warn install-scripts puppeteer@24.43.1 (postinstall: node install.mjs) == Problem 2 == puppeteer 24 (grunt-contrib-qunit 10.x) is incompatible with Node 26 due to an issue with extract-zip, which was not fixed until puppeteer 25. puppeteer 25 drops support for Node 18, which means we have to use either grunt-contrib-qunit 10 (puppeteer 24) or 11 (puppeteer 25) Ref https://github.com/puppeteer/puppeteer/issues/14957 == Problem 3 == `npm install` does not honor engines.node requirements correctly This was seemingly fixed in npm 10.8, and the last Node.js 18 release is 18.20.8 (March 2025) which bundled npm 10.8.2. Yay? Ref https://github.com/npm/cli/issues/6743 Ref https://github.com/nodejs/node/commits/v18.x/deps/npm
1889 of 2088 relevant lines covered (90.47%)
3259.47 hits per line
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|