Why node-fetch and uuid pkgs?

[itxtoledo]

This library is supposedly intended for node-js, so why not use the uuid generator from the native "crypto" module and the native "fetch" from node instead of node-fetch?

Example: Using crypto for UUID and fetch for HTTP Requests in Node.js

// Import required modules
const { randomUUID } = require('crypto'); // Native UUID generator
const fetch = require('node:fetch'); // Native fetch module

// Generate a UUID
const uuid = randomUUID();
console.log(`Generated UUID: ${uuid}`);

// Use fetch to make an HTTP GET request
const fetchExample = async () => {
  try {
    const response = await fetch('https://jsonplaceholder.typicode.com/todos/1');
    if (!response.ok) {
      throw new Error(`HTTP error! Status: ${response.status}`);
    }
    const data = await response.json();
    console.log('Fetched Data:', data);
  } catch (error) {
    console.error('Error fetching data:', error);
  }
};

// Call the fetch example
fetchExample();

[andreagostinho-meli]

Hi @itxtoledo!
The node-fetch and uuid modules have been around for a while in the SDK.
We appreciate your suggestion! If we work on updating those modules in the future, we will take your suggestion into account 🙂
However, we currently have no plans to change them in the SDK.

Thank you!