Bug - "Write after end" using filestack-js upload method

[ehubbell]

I have a server application that uploads .webp images from a public directory to Filestack for cloud optimization and storage. And, I’m running into an issue where a couple of specific images won’t upload and instead generate the following error that crashes the node process outside the try / catch statement I have wrapping the upload method:

About:

node v22.13.1
filestack-js v3.37.5

Method:

	static get client() {
		return Filestack.init(process.env.FILESTACK_API_KEY);
	}

	static async upload(filePath) {
		try {
			const upload = await this.client.upload(filePath);
			logger.log('Filestack upload: ', upload.url);
			return upload.url;
		} catch (e) {
			logger.error(e);
			throw e;
		}
	}

Error:

playbooks-server  | Error [ERR_STREAM_WRITE_AFTER_END]: write after end
playbooks-server  |     at write_ (node:_http_outgoing:955:11)
playbooks-server  |     at ClientRequest.write (node:_http_outgoing:904:15)
playbooks-server  |     at HttpWritableStream.HttpWritableStream._write (/playbooks-server/node_modules/filestack-js/build/main/lib/src/lib/request/adapters/http.ts:54:18)
playbooks-server  |     at doWrite (node:internal/streams/writable:598:12)
playbooks-server  |     at clearBuffer (node:internal/streams/writable:783:7)
playbooks-server  |     at onwrite (node:internal/streams/writable:653:7)
playbooks-server  |     at callback (node:internal/streams/writable:766:21)
playbooks-server  |     at afterWrite (node:internal/streams/writable:710:5)
playbooks-server  |     at onwrite (node:internal/streams/writable:688:7)
playbooks-server  |     at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:105:10)
playbooks-server  |     at WriteWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
playbooks-server  |   code: 'ERR_STREAM_WRITE_AFTER_END'
playbooks-server  | }

I tried uploading the culprit images via the Filestack picker using our web application and everything works okay. I’ve checked the images and nothing stands out. Basic vector files exported to the webp format. I also experienced the issue when using jpeg images.

Do you know why this would be happening and / or how to fix the issue?