[vdusek]

ActorInput was an alias for object, so a Date, Map, Set or function compiled and then went out as a wrong body or threw. It's now Dictionary | Dictionary[] | Uint8Array, which is the type suggested in #1054 plus Uint8Array. The extra member keeps raw-bytes input compiling (a Buffer sent with a contentType, see #277 and #1078).

This is a breaking change for input declared as an interface. Interfaces get no implicit index signature, so they don't match Dictionary. The v3 migration guide shows the fix, either a type alias or a spread ({ ...input }).

A type test pins the accepted and rejected shapes.

This doesn't touch contentType, the other half of #1054. The platform still stores the INPUT record under the content type it receives.

Closes: #1054

✍️ Drafted by Claude Code

[github-actions]

⚠️ There are broken links in the documentation.

See more at https://github.com/apify/apify-client-js/actions/runs/36873948690#summary-110408474249

[vdusek]

@B4nan, could you please give this type a quick look (I'm not able to review it.)?

export type ActorInput = Dictionary | readonly Dictionary[] | Uint8Array | ArrayBuffer;

vs. your suggested version:

type Dictionary = Record<PropertyKey, unknown>;
type ActorInput = Dictionary | Dictionary[];

[B4nan]

Your version is fine, it's a superset of what I suggested. readonly Dictionary[] still accepts mutable arrays, and the bytes have to be there because serializeBody sends them as they are. Without them you couldn't use contentType with a non-JSON input.

One nit: at runtime isBuffer lets any typed array through, while the type only allows Uint8Array. I wouldn't bother widening it.