Transition from Axios to Fetch API

[rlajous]

📃 Description

We are in the process of migrating from Axios to the Fetch API in an effort to improve the compatibility of our libraries and reduce external dependencies.

💡 Motivation

The aim is to adapt our library to use Fetch, a native API of modern browsers and also available in Node.js environments from certain versions onwards. This allows us to have a more lightweight and standardized solution.

🚀 Benefits

1. Standardization: Using Fetch, built into most modern browsers, we promote standardization and reduce our reliance on third-party libraries.
2. Lightweight: Eliminating the need for Axios significantly reduces the overall size of our library, resulting in faster load times.
3. Future-proof: This transition makes our library more sustainable and future-proof as more developers adopt Fetch.

❗ Requirements

For the use of the Fetch API in a Node.js environment, our library now requires Node.js version X or later due to Fetch API compatibility from this version onwards.

🏁 Conclusion

This change aligns with our commitment to adapt to modern standards, optimize our libraries, and deliver a more robust and efficient tool for our users.

🗣️ Feedback

We would love to hear your feedback and suggestions about this transition. Also, are there other areas of improvement we could consider for future updates?

[rlajous]

We are still missing the ability to remove the dependency from moments.