migrate tests from node-fetch to fetch directly#15233
migrate tests from node-fetch to fetch directly#15233LukeSheard wants to merge 4 commits intomainfrom
Conversation
🦋 Changeset detectedLatest commit: 660e603 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This stack of pull requests is managed by Graphite. Learn more about stacking. |
📦 CLI Tarball ReadyThe Vercel CLI tarball for this PR is now available! Quick TestYou can test this PR's CLI directly by running: npx https://vercel-qnwhdgtz0.vercel.sh/tarballs/vercel.tgz --helpUse in vercel.jsonTo use this CLI version in your project builds, add to your {
"build": {
"env": {
"VERCEL_CLI_VERSION": "vercel@https://vercel-qnwhdgtz0.vercel.sh/tarballs/vercel.tgz"
}
}
}Python Runtime WheelA Python Workers WheelA |
🧪 Unit Test StrategyComparing: Strategy: Code changed outside of a package - running all unit tests Affected packages - 15 (38%)
Unaffected packages - 25 (63%)
Results
This comment is automatically generated based on the affected testing strategy |
02d0e3f to
577ec30
Compare
2fe8f35 to
1092c73
Compare
1092c73 to
6e7bf78
Compare

Overview
Replace usage of node-fetch with fetch
Note
Low Risk Change
This PR migrates test files from node-fetch to native fetch API, containing only import removals, test utility updates, and minor type casting changes with no security or business logic impact.
Risk assessment for commit 660e603.