yarn install better-sqlite3 build fails under Node.js 23.6.0

[MikeMcC399]

Issue

yarn install fails under Node.js 23.6.0 ("Current" version, released Oct 15, 2024)

better-sqlite3@npm:10.1.0 couldn't be built successfully

Attempting to update .github/workflows/ci.yml to run also on Node.js 23 shows that it fails under ubuntu-latest, macos-latest and windows-latest.

Following the instructions in CONTRIBUTING locally and running yarn install in Ubuntu 24.04.1 LTS reproduces the failure also.

Logs

Run corepack yarn install --immutable
➤ YN0000: · Yarn 4.3.1
➤ YN0000: ┌ Resolution step
Resolution step
➤ YN0000: └ Completed
➤ YN0000: ┌ Post-resolution validation
Post-resolution validation
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
Fetch step
➤ YN0000: └ Completed in 2s 582ms
➤ YN0000: ┌ Link step
Link step
➤ YN0009: better-sqlite3@npm:10.1.0 couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-7c8502a7/build.log)
/tmp/xfs-7c8502a7/build.log
➤ YN0000: └ Completed in 1m 11s
➤ YN0000: · Failed with errors in 1m 14s
Error: Process completed with exit code 1.

[arcanis]

This isn't related to Corepack. The issue likely comes from better-sqlite3 itself, although it's difficult to say since you didn't paste the log file described in the output.

[MikeMcC399]

@arcanis

This isn't related to Corepack. The issue likely comes from better-sqlite3 itself, although it's difficult to say since you didn't paste the log file described in the output.

The issue appears to be due to an older version of better-sqlite3 which corepack is configured to use. If you would like to re-open this issue I can propose some changes to the corepack configuration which would resolve the issue. (Basically drop Node.js 21 support and upgrade better-sqlite3).

[MikeMcC399]

The suggestion seems to work. See https://github.com/MikeMcC399/corepack/actions/runs/12744446123 for test run.

[MikeMcC399]

• Moved discussion to Update better-sqlite3 to >= 11.5.0 #592 with some concrete and detailed suggestions for resolution of this issue

[MikeMcC399]

@arcanis

• This issue is resolved in PR chore!: remove Node.js 21.x from the range of supported versions #594