Node.js (server-side) SDK 6.x to 7.0 migration guide

Overview

This topic summarizes changes and explains how to adapt code that uses a 6.x version of the Node.js (server-side) SDK to use version 7.0 or later.

Version 7.0 includes several breaking changes. Additionally, if you use the Relay Proxy, you must update your Relay Proxy to version 7.0 before you update your SDK to version 7.0. To learn more, read the Relay Proxy 7.0 release notes. To upgrade to the latest Relay Proxy version, visit Relay Proxy releases on GitHub.

Before you migrate to version 7.0, update to the latest 6.x version. Some of the changes that are mandatory in 7.0 were originally added in a 6.x version and made optional.

If you update to the latest 6.x version, deprecation warnings appear in areas of your code that need to be changed for 7.0. You can update them at your own pace while still using 6.x, rather than migrating everything simultaneously. To learn more about updating to the latest 6.x version, visit the SDK's GitHub repository.

Understanding contexts

Many LaunchDarkly customers create targeting rules for feature flags based on a variety of different information, including attributes pertaining to users, organizations, devices, and more. In previous versions of the LaunchDarkly SDK, you could define this information in a user object, using a combination of built-in and custom attributes. Now you can define this information in a more structured way, using contexts.

Each context has a required attribute called kind that you can use to categorize context instances for targeting and Experimentation. You can also add other attributes. Attributes can be strings, booleans, numbers, arrays, or JSON objects.

When you evaluate a feature flag within your application, the flag's targeting rules use information from one or more kinds of contexts. For example, you may know:

• the username, first name, last name, and email address of a person, as part of a context with kind of "user"
• the company, department, and location of an organization, as part of a context with kind of "organization"
• the device, model, and operating system of an environment, as part of a context with kind of "device"

This new version of the LaunchDarkly SDK requires you to evaluate feature flags using an evaluation context, which is an object containing one or more contexts.

To learn more about contexts, read Contexts.

Migrating from users to contexts

The 7.0 version of this SDK lets you use contexts. When you migrate from version 6.x, replace every instance of a user with a context. If there are any instances of user you do not replace, the 7.0 version of the SDK will convert each LDUser parameter it receives to LDContext and call the LDContext-specific version of the method.

The primary differences between working with users and working with contexts include the following:

• Changes to flag evaluation: The methods for evaluating flags now require contexts, rather than users.
• Create contexts, not users: Where you previously created users, now you must create contexts.
• Changes to attributes: There are now fewer built-in attributes. You can still add as many custom attributes as you like, although the format has changed slightly. A flag's targeting rules can now address fields within a JSON object.
• Changes to private attributes: You can mark specific attributes of a context as private, either across all contexts of any kind, or within a particular context or context kind.
• Changes to alias events: The alias method has been removed.

Understanding changes to flag evaluation

The methods for evaluating flags and determining flag evaluation reasons have changed slightly. The 7.0 version of the SDK includes the following changes:

• The variation and variationDetail methods now take a context, rather than a user, as a parameter. To learn more, read variation API docs and the variationDetail API docs.
• The USER_NOT_SPECIFIED evaluation error code was previously defined as, the user object or user key was not provided. It has been redefined to mean that the context was not provided or was invalid.

Here's how to evaluate a flag using a context:

Understanding differences between users and contexts

Where you previously created users, now you must create contexts.

Here's how to construct a basic context, as compared with constructing a user:

Here's how to construct a basic context, with a context kind of something other than "user":

Here's how to construct a multi-context, which includes multiple context kinds:

Understanding changes to built-in and custom attributes

This section describes the changes to built-in and custom attributes in the 7.0 version of the SDK.

Working with built-in and custom attributes

In previous SDK versions, the user object included several built-in attributes for describing the user. It also included optional custom attributes, which you could add to a custom object within the user object and then populate.

In version 7.0, the only built-in attributes are kind, key, name, and anonymous. Kind, key, and name are strings, and anonymous is a boolean.

You can define additional attributes for a context by passing in a name and value for each. Additional attributes can be any JSON type, including boolean, number, string, array, or object. In version 7.0, you do not need to add custom attributes within a custom object.

Here's how to construct a context with additional attributes, as compared with constructing a similar user:

Referencing properties of an attribute object

In previous versions of the SDK, if you set the value of a user's custom attribute to an object, you could not reference that object in evaluations. In version 7.0, if a context attribute's value is a JSON object, you can reference properties of that object as the attribute in the targeting rules for a flag or segment.

Here's how to add object attributes to a context:

In your flag or segment targeting, use / as the delimiter to refer to specific object fields. For example, you can use /address/city in your targeting. To learn more, read Target with flags.

Removing the secondary attribute

In previous versions of the SDK, you could set the value of a user's secondary attribute, as an optional secondary key for a user. The SDK would incorporate this attribute into the variation bucket assignment hash.

In version 7.0, the secondary attribute has been removed. If you were previously using this attribute as part of distinguishing percentage rollouts, that will no longer work for your users.

Understanding changes to private attributes

As in previous versions of the SDK, you can mark specific attributes of a context as private. This restricts the context data your application sends to LaunchDarkly, while still using that data for flag targeting.

In version 7.0, there are two scopes for which you can mark attributes as private:

• Across all contexts of any context kind. You might use this if you want to ensure that the SDK never sends an "email" attribute to LaunchDarkly, no matter whether it occurs in a user context, an organization context, or something else.
• Within a particular context or context kind. You might use this if you want an "email" attribute to be private in a user context, but not in an organization context.

In version 7, you can make all attributes private with the same configuration as in previous versions of the SDK. That behavior has not changed between SDK versions. Making select attributes private has changed. An example appears below.

In this example, the "email" and "address" attributes are private for all contexts:

To learn more, read the SDK's API documentation for allAttributesPrivate and privateAttributes.

Here's how to mark an attribute as private for a particular context:

For attributes that are objects, you can mark specific fields private, using the / delimiter followed by the attribute name, then the / delimiter followed by the JSON property within the value.

For example, for the attribute "address": { "street": "Main St", "city": "Springfield" }, you could set just the /address/street as private.

The privateAttributeNames attribute that existed in a user object in version 6.x has been renamed to privateAttributes in version 7.0. It has moved from the top level of a user object into the _meta object within a context. To learn more, read privateAttributes.

Understanding changes to alias events

In previous versions of the SDK, multiple user objects could represent one person. For example, this could happen the first time a person logged in to your application. The person might be represented by an anonymous user before they logged in, and a different user after they logged in. You could associate these two LaunchDarkly users by sending an alias event in the SDK.

With the introduction of contexts, the person in this scenario is represented by two different context kinds. For example, before they log in, they might be represented by a device context. After they log in, they might be represented by a multi-context, for example, by one context kind based on their device and simultaneously by another context kind based on their user information.

The 7.0 version of the SDK removes the ability to send an alias event. If you currently alias users, you will need to remove this code when you migrate to version 7.0.

If you want to continue associating two contexts with each other, you can use two different context kinds, and then identify a multi-context that includes both individual contexts when you want the association to occur. Unlike the aliasing method, the association doesn't persist between calls. You must send the contexts you want to associate in each variation or identify call and each track call.

Here's how:

Understanding changes to configuration options

In the 7.0 version of the SDK, several configuration options have changed:

• The privateAttributes and allAttributesPrivate configuration options both now apply to all contexts of any context kind. To learn more, read Understanding changes to private attributes.
• privateAttributeNames is now called privateAttributes. To learn more, read Understanding changes to private attributes.
• The inlineUsersInEvents option has been removed.
• The userKeysCapacity and userKeysFlushInterval options are now deprecated. They have been replaced in this version with contextKeysCapacity and contextKeysFlushInterval, respectively. If both are provided, the newer context configuration options will take precedence.
• ifMatch, ifNotMatch, andMatch, and andNotMatch all require a context kind as their first parameter. This is a breaking change.

Understanding what was deprecated

All types and methods that were marked as deprecated in the last 6.x release have been removed from the 7.0 release. If you were using these with a recent version previously, you should already have received deprecation warnings at compile time, with suggestions about their recommended replacements.

For a full list of deprecated types and methods, read the release notes in GitHub.