customerio-node: ERR_INVALID_ARG_TYPE: The listener argument must be of type Function on track()

TL;DR

For "[ERRINVALIDARG_TYPE]: The "listener" argument must be of type Function. Received type object": upgrade to 3.0.3 or later. The maintainer reproduced it, shipped the fix in customerio-node@3.0.3 (tested first as 3.0.3-beta.1), and the reporter confirmed the fix.

[ERR_INVALID_ARG_TYPE]: The "listener" argument must be of type Function. Received type object

Steps

1. What was going on

Following the customerio-node docs for event tracking in Node.js, new TrackClient(siteId, apiKey, { region: RegionUS }) then await trackClient.track(userId, { name, data }) throws [ERR_INVALID_ARG_TYPE]: The "listener" argument must be of type Function. Received type object. The code matched the README example exactly.

2. What fixed it

This was a bug in the library itself: the track request pipeline passed a non-function where Node's EventEmitter expected a listener. The maintainer reproduced it, shipped the fix in customerio-node@3.0.3 (tested first as 3.0.3-beta.1), and the reporter confirmed the fix. Upgrade to 3.0.3 or later.

When to use

You are seeing this: What was going on Following the customerio-node docs for event tracking in Node.js, new TrackClient(siteId, apiKey, { region: RegionUS }) then await trackClient.track(userId, { name, data }) throws [ERR\INVALID\ARG\TYPE]: The "listener" argument must be... Use this skill when you run into "customerio-node: ERRINVALIDARGTYPE: The listener argument must be of type Function on track()".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: customerio-node 3.0.3, as 3.0.3-beta.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In the thread, the question was: Following the customerio-node docs for event tracking in Node.js, new TrackClient(siteId, apiKey, { region: RegionUS }) then await trackClient.track(userId, { name, data }) throws [ERR_INVALID_ARG_TYPE]: The "listener" argument must be of type Function. Received type object. The code matched the README example exactly. The verified resolution: This was a bug in the library itself: the track request pipeline passed a non-function where Node's EventEmitter expected a listener. The maintainer reproduced it, shipped the fix in customerio-node@3.0.3 (tested first as 3.0.3-beta.1), and the reporter confirmed the fix. Upgrade to 3.0.3 or later. Thread: https://vectle.com/threads/thr_FkZluFerAdgHWu7wGshfnA