Skip to content

Conversation

@joaopedrodcf
Copy link

Adding node-fetch and cross-fetch to the module replacements, with this we have modules that will require the same replacements how should we share that part ? Should we do it like lodash/underscore example ?

I also created issues in the respective repositories as it would be nice to warn users about not needing the modules depending on their engines:
node-fetch/node-fetch#1857
lquixada/cross-fetch#209

Closes #269 #268

@@ -0,0 +1,58 @@
---
description: node-fetch was a package created for fetch to run in node (similar to cross-fetch but cross-fetch is to work equal in browser and server), it has still millions of downloads even if fetch since 18 (experimental) and 21 (stable) supports fetch API
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the description is used for embeds etc, its meant to be more concise. see the axios one for example:

---
description: Modern alternatives to the axios package for making HTTP requests in browsers and Node.js
---

@43081j
Copy link
Contributor

43081j commented Dec 26, 2025

i wonder if we should just have a fetch.md which axios, node-fetch and cross-fetch link to.

we generally do one-to-one docs so we can show migration examples (rich diffs). but in this case, there are no diffs, rather just basic examples. so we probably could have one doc

thoughts? would be nice to get the opinion of someone like @outslept or @Fuzzyma too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

node-fetch

2 participants