Releases: customerio/customerio-node
Releases · customerio/customerio-node
v3.0.0
-
(BREAKING) Remove the dependency on
request
(#62)- We don't expect this to break many consumers of
customerio-node
. Unless you were usingrequest
specific options, you don't need to make any changes.
- We don't expect this to break many consumers of
-
(BREAKING) Return an
Error
instance for non-2XX
status codes (#62)- We don't expect this to break many consumers of
customerio-node
. Unless you were usinginstanceof
to check the type of error returned from track or api methods, you don't need to make any changed.message
,statusCode
,response
, andbody
are still accessible as properties on the error.
- We don't expect this to break many consumers of
-
(BREAKING)
trackAnonymous
now requires ananonymous_id
and cannot trigger campaigns. If you previously used anonymous events to trigger campaigns, you can still do so directly through the API. We now refer to anonymous events that trigger campaigns as "invite events". -
(BREAKING) Restructure the package to have a single entry point, rather than three. This is more of a standard package structure, and is more future-proof. (#63)
-
Return a readable message when the server returns an array of errors instead of
Unknown error
(#62)