-
Notifications
You must be signed in to change notification settings - Fork 24
tests: Replace use of preq with native fetch #253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
If we increase the node version to 18(LTS, Maintainance mode) or later, 'fetch' API is standardized and stable in node. No need for an external library. |
Yes, but other parts of the library aren't yet compatible with Node 18, so we can't do that right now (until I or someone else has the time to fix those incompatibilities). |
|
Not sure what's causing the errors here, but as I'm looking into preq for an unrelated issue, I thought I should note it differs from fetch in at least two ways: Preq is wrapping errors, so we might loose some logging features upstream if those are not replaced upstream; Preq uses another defunct library called requestretry to automatically retry requests once after a short time out. |
Yeah, those two are things to bear in mind for downstream users if they're just |
|
Weird this works in 20 but not 18 now. Should we just have this be 7.0.0. and drop 18? :) |
Yeah, I'm not quite sure what's going on there – possibly an upstream library version issue? Anyway, let's do that (but in a different PR); most users have bumped by now. Edit: Proposed in #263 . |
Bug: T293853
Bug: T309772