Consider replacing node-libcurl with modern HTTP clients to avoid native build issues

[Jeongyong-park]

node-libcurl depends on libcurl, a native C++ library, which often leads to build and compatibility issues when upgrading Node.js versions or switching platforms (e.g., Windows, ARM).

These native dependencies increase installation complexity and can break CI/CD pipelines or local development environments during Node upgrades.

Migrating to modern, fully JavaScript-based HTTP clients like [undici](https://github.com/nodejs/undici) (the official HTTP client for Node.js) or [got](https://github.com/sindresorhus/got) would eliminate these issues. They provide robust and high-performance alternatives with better support for async/await and native promise-based APIs.

Replacing node-libcurl could significantly improve maintainability, developer experience, and cross-platform compatibility.

[pierotofy]

Would you be interested in helping with this?

[spwoodcock]

I agree replacing libcurl usage would probably be the best option.

But if such a big refactor is not possible currently, updating libcurl is probably now an option since JCMais/node-libcurl#423 is fixed 👍