fix: Force 2.7.0 version of node-fetch (SCR-604) #1480
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To avoid "socket hang up" / ECONNRESET on consecutive requests with Node.js 19 and Node.js 20 node-fetch/node-fetch#1735 We did not have this problem before because projects using cozy-client had 2.7.0 in their yarn.lock even if lower version was specified in package.json.
|
Since Cozy is running on node 20, I think we should delete the dep to node-fetch since WDYT? |
|
What is the status of this PR @doubleface ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To avoid "socket hang up" / ECONNRESET on consecutive requests with
Node.js 19 and Node.js 20
node-fetch/node-fetch#1735
We did not have this problem before because projects using cozy-client
had 2.7.0 in their yarn.lock even if lower version was specified in
package.json.