fix: switch to undici for requests to fix stream close errors

[austinkelleher]

Fixes #626

When updating WPT resources, the wpt command would sometimes throw a ERR_STREAM_PREMATURE_CLOSE error. Switching to undici fixes this issue.

The undici fetch function is only supported on Node 16+. After discussing with the team, we agreed that dropping support for Node 14 in this tool was acceptable (#626 (comment)).

➜  node git:(main) ✗ ./node /Users/austinkelleher/Documents/open-source/node-core-utils/bin/git-node.js wpt resources
---------------------- Checking updates for resources... -----------------------
Last local update for resources is fbf1e7d24776
✔  Last update in upstream is 66933c819b6e
✔  Read asset list, 165 files in total.
Excluded 133 files, 32 files to write.
--------------- Writing assets to test/fixtures/wpt/resources... ---------------
✔  Downloaded 32 assets.
✔  Updated test/fixtures/wpt/versions.json
✔  Updated test/fixtures/wpt/README.md
✔  Updated test/fixtures/wpt/LICENSE.md.

[codecov]

Codecov Report

Base: 83.41% // Head: 83.41% // No change to project coverage 👍

Coverage data is based on head (5b81893) compared to base (51a3b24).
Patch has no changes to coverable lines.

❗ Current head 5b81893 differs from pull request most recent head a9c0974. Consider uploading reports for the commit a9c0974 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #666   +/-   ##
=======================================
  Coverage   83.41%   83.41%           
=======================================
  Files          37       37           
  Lines        4131     4131           
=======================================
  Hits         3446     3446           
  Misses        685      685           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[aduh95]

The commit message would need to be updated to reflect that this is a breaking change. Calling it fix is probably not right as we're dropping support for Node.js 14.x. We may want to add an "engines": { "node": ">=16.8.0" }¹ entry in the package.json as well.

Footnotes

1. according to https://github.com/nodejs/undici#undicifetchinput-init-promise, that's the minimum Node.js version which is compatible. ↩

[targos]

For whoever is going to merge: add a line with BREAKING CHANGE: description of the change to the commit message to make the version bump happen.

[austinkelleher]

@aduh95 @targos Thanks for all of the great feedback. Let me know if you want me to make updates to the commit history.

Can someone please trigger the CI for me? Thanks!