-
Notifications
You must be signed in to change notification settings - Fork 17
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
Remove isomorphic-fetch due to vulnerabilities #28
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,13 @@ | ||
import 'isomorphic-fetch'; | ||
import nodeFetch from 'node-fetch'; | ||
import { version as cliVersion } from '../package.json'; | ||
|
||
if (!global.fetch) { | ||
global.fetch = module.exports; | ||
global.Response = nodeFetch.Response; | ||
global.Headers = nodeFetch.Headers; | ||
global.Request = nodeFetch.Request; | ||
} | ||
|
||
Comment on lines
+4
to
+10
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is just what isomorphic-fetch does on commonjs. Perhaps it could be hidden somehow, it feels kind of nasty out here. Alternatively, the fetch implementation could be injected from outside, but it was overall a bigger change code and architecture-wise. |
||
const delay = t => new Promise(resolve => setTimeout(resolve, t)); | ||
|
||
const RETRY_STATUS = [429, 500, 502, 503, 504]; | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The v3 version requires ESM, but this one should be fine security-wise.