Releases: Kameleoon/client-nodejs
Releases · Kameleoon/client-nodejs
NodeJS SDK 5.1.0
Features
- Enhanced top-level domain validation within the SDK. The implementation now includes automatic trimming of extraneous symbols.
- Enhanced
logging
:- Introduced
log levels
:None
Error
Warning
Info
Debug
- Added support for
custom logger
implementations.
- Introduced
- Introduced new evaluation methods for clarity and improved efficiency when working with the SDK:
- Introduced methods replace the deprecated ones:
- A new version of the
isFeatureFlagActive
method now has a new overload, which contains an optionaltrack
parameter for managing the assigned variation tracking (default:true
).
Patch Changes
- [
UniqueIdentifier
][uniqueidentifier] data is now correctly exported from the SDK - Updated dependencies
- @kameleoon/[email protected]
NodeJS SDK 5.0.2
Patch Changes
- Fixed build issue resulting in potential issues when using any targeting condition with
Exclude
option - Updated dependencies
- @kameleoon/[email protected]
NodeJS SDK 5.0.1
Patch Changes
- Fixed an issue with the
Page URL
andPage Title
targeting conditions, where the condition evaluated all previously visited URLs in the session instead of only the current URL, corresponding to the latest addedPageView
NOTE: This change may impact your existing targeting. Please review your targeting conditions to ensure accuracy. - Updated dependencies
- @kameleoon/[email protected]
NodeJS SDK 5.0.0
Breaking Changes
isUniqueIdentifier
parameter has been removed from methodsflush
,getRemoteVisitorData
andtrackConversion
- Previously deprecated method
onConfigurationUpdate
has been removed from SDKs. UseonEvent
method withEventType.ConfigurationUpdate
to achieve the same effect. - Previously deprecated field
domain
ofSDKConfiguration
has been removed from SDKs. UsecookieDomain
field ofSDKConfiguration
instead. - Parameter
text
ofKameleoonResponseType
used in customrequester
implementation is now mandatory, for the vast majority of implementations likefetch
,axios
ornode-fetch
it won't require any changes. - SDK stopped using
node-fetch
dependency - that leads to externalrequester
becoming mandatory dependency. To make sure SDK works correctly make sure to install@kameleoon/nodejs-requester
package or provide your implementation. Usesdk-installer
for more detailed information. externalRequestDispatcher
was removed from an SDK - all its functionality can be covered by using customrequester
implementation.- SDK parameters
integrations
was removed along with its fieldexternalClientConfiguration
, use customrequester
withRequestType.ClientConfiguration
to provide custom configuration instead. - Static method
KameleoonUtils.getClientConfigurationUrl
was removed - configuration url can be accessed usingrequester
Features
- Added new
UniqueIdentifier
data to be used instead of removedisUniqueIdentifier
parameters in some methods - Added new
SDKConfiguration
parametertrackingInterval
to set the interval between SDK tracking network requests in milliseconds, default value is 1000, which is also maximum interval, minimum value is 100 FeatureVariableType
returned from the methods obtaining feature flag variables can now have two newVariableType
s -VariableType.JS
containing astring
of JavaScript code andVariableType.CSS
containing a string with CSS code
Patch Changes
getEngineTrackingCode
method now correctly setstriggerExperiment
parameter based on variable types- Updated dependencies
- @kameleoon/[email protected]
NodeJS SDK 4.4.8
Patch Changes
- It's now possible to create several SDK instances with different site codes
- Updated dependencies
- @kameleoon/[email protected]
NodeJS SDK 4.4.7
Patch Changes
- Fixed the issue with mapping identifier Custom Data not being set correctly after reading SDK configuration from a storage
- Updated dependencies
- @kameleoon/[email protected]
NodeJS SDK 4.4.6
Patch Changes
- Fixed an issue that caused duplicate entries in feature flag results for both anonymous and authorized/identified visitors during data reconciliation. This problem occurred when custom data of type mapping ID was not consistently sent for all sessions.
- Updated dependencies
- @kameleoon/[email protected]
NodeJS SDK 4.4.5
Patch Changes
- Fix previous release, which didn't contain all the described changes
- Updated dependencies
- @kameleoon/[email protected]
NodeJS SDK 4.4.4
Patch Changes
- Improved random generation for
nonce
values - Updated dependencies
- @kameleoon/[email protected]
NodeJS SDK 4.4.3
Patch Changes
- Fixed the issue of
addData
method throwing an error after usingsetLegalConsent
getVisitorCode
now sets the visitor code to serverresponse
, customoutput
or Next.jscookie
object correctly, when the visitor code was initially retrieved from it- Updated dependencies
- @kameleoon/[email protected]