-
Notifications
You must be signed in to change notification settings - Fork 21
Open
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
-
Is this a client library issue or a product issue?
This issue is related to the client library for Node.js. -
Did someone already solve this?
- This issue is solved in node-fetch@3.2.10.
- Do you have a support contract?
No.
If the support paths suggested above still do not result in a resolution, please provide the following details.
Environment details
- OS: Windows 11
- Node.js version: 20.7.0
- npm version: 10.1.0
gax-nodejsversion: 3.6.1
Steps to reproduce
- Create a new Node.js project
- Install node-fetch versions ranging between 3.1.0 and 3.2.9 or packages that depend on such versions of node-fetch.
This bug affects all versions of node-fetch from 3.1.0 until 3.2.9.
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.