Switching to formdata-node in version 4.0.4 breaks sending large files via ReadableStream

[Lunatic174]

Description:

Starting from version 4.0.4 of jira.js, the library replaced form-data with formdata-node to improve ESM compatibility. The change was introduced as part of #327 to resolve compatibility issues with ESM projects. While this change resolves compatibility issues with ESM projects, it introduces a regression: the inability to upload large files via Node.js ReadableStream without loading the entire file into memory and breaks backward compatibility.

In previous versions (e.g., 3.0.5), form-data allowed seamless usage of ReadableStream for large file uploads. However, formdata-node does not natively support Node.js ReadableStream, and the same code now results in errors when attempting to upload attachments.

Steps to Reproduce:

1. Upgrade to jira.js version 4.0.4 or higher.
2. Create a file as a ReadableStream in Node.js.
3. Attempt to upload the file as an attachment to Jira using the provided API.
4. Observe that the upload fails with error "Failed to execute 'append' on 'FormData': parameter 2 is not of type 'Blob'."

Example Code:

Code that worked in version 3.0.5:

import { Version3Client } from 'jira.js';
import fs from 'fs';

const client = new Version3Client({
  host: 'https://your-instance.atlassian.net',
  authentication: {
    basic: {
      email: 'your-email@example.com',
      apiToken: 'your-api-token',
    },
  },
});

const fileStream = fs.createReadStream('./large-file.txt');

(async () => {
  try {
    const response = await client.issueAttachments.addAttachment({
      issueIdOrKey: 'PROJECT-123',
      attachment: {
        file: fileStream,
        filename: 'large-file.txt',
      },
    });
    console.log('Attachment uploaded successfully:', response);
  } catch (error) {
    console.error('Error uploading attachment:', error.message);
  }
})();

The same code will fail in 4.0.4 with error "Failed to execute 'append' on 'FormData': parameter 2 is not of type 'Blob'."

Expected Behavior:

Files should be uploaded seamlessly using Node.js ReadableStream, as was possible in version 3.0.5.

Actual Behavior:

Uploads fail when attempting to use Node.js ReadableStream for file attachments. The same code that worked in version 3.0.5 now results in errors.

Environment:

jira.js version: 4.0.4 or later
Node.js version: 20.11.0
OS: macOS Sequoia 15.2

[MrRefactoring]

Fix will be published in v4.0.6. Thank you for the issue

[Lunatic174]

Thank you for the fix!
I just checked it, and it works now. However, I noticed a potential issue with memory usage because files are uploaded through memory.

I believe this would only be relevant for large files, so I created a separate issue #353 to address it.
Feel free to take a look if you think it's worth discussing further.