Update undici#206
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 3c2d0f8. Configure here.
| "ts-node": "^10.9.1", | ||
| "typescript": "^5.1.6", | ||
| "undici": "^5.8.0" | ||
| "undici": "^8.3.0" |
There was a problem hiding this comment.
Tests need newer Node
Medium Severity
Upgrading the test-only undici devDependency to v8 makes npm test depend on Node >=22.19.0, because Jest imports undici in __tests__, while engines still allows Node >=16. Environments on Node 16–22.18 that satisfied engines and worked with undici v5 can fail when loading or running tests.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 3c2d0f8. Configure here.
There was a problem hiding this comment.
Our tests are run with a newer version of Node, so I'm okay with this.
I do not want to stay on an old version of undici, but I don't want to unnecessarily bump the required version of Node for this package purely for a test dependency. It's likely that we should bump that to a newer version of Node that is LTS, but that's a separate discussion.


This updates
undicito the latest available version, resolving a couple of reported warnings innpm audit.These issues do not apply to our usage of
undiciwhich is purely in tests that we maintain, but it's still good to stay up to date.