@openfeature/server-sdk - npm Package Compare versions

Comparing version 1.16.0 to 1.16.1

package.json

		{
		"name": "@openfeature/server-sdk",
		"version": "1.16.0",
		"version": "1.16.1",
		"description": "OpenFeature SDK for JavaScript",
		@@ -5,0 +5,0 @@ "main": "./dist/cjs/index.js",

README.md

		@@ -19,4 +19,4 @@ <!-- markdownlint-disable MD033 -->
		<!-- x-release-please-start-version -->
		<a href="https://github.com/open-feature/js-sdk/releases/tag/server-sdk-v1.16.0">
		<img alt="Release" src="https://img.shields.io/static/v1?label=release&message=v1.16.0&color=blue&style=for-the-badge" />
		<a href="https://github.com/open-feature/js-sdk/releases/tag/server-sdk-v1.16.1">
		<img alt="Release" src="https://img.shields.io/static/v1?label=release&message=v1.16.1&color=blue&style=for-the-badge" />
		</a>
		@@ -68,3 +68,3 @@ <!-- x-release-please-end -->

		> [!NOTE]
		> [!NOTE]
		> `@openfeature/core` contains common components used by all OpenFeature JavaScript implementations.
		@@ -101,11 +101,12 @@ > Every SDK version has a requirement on a single, specific version of this dependency.
		\| ------ \| ------------------------------------------------------------------- \| ------------------------------------------------------------------------------------------------------------------------------------- \|
		\| ✅ \| [Providers](#providers) \| Integrate with a commercial, open source, or in-house feature management tool. \|
		\| ✅ \| [Targeting](#targeting) \| Contextually-aware flag evaluation using [evaluation context](/docs/reference/concepts/evaluation-context). \|
		\| ✅ \| [Hooks](#hooks) \| Add functionality to various stages of the flag evaluation life-cycle. \|
		\| ✅ \| [Logging](#logging) \| Integrate with popular logging packages. \|
		\| ✅ \| [Domains](#domains) \| Logically bind clients with providers. \|
		\| ✅ \| [Eventing](#eventing) \| React to state changes in the provider or flag management system. \|
		\| ✅ \| [Shutdown](#shutdown) \| Gracefully clean up a provider during application shutdown. \|
		\| ✅ \| [Transaction Context Propagation](#transaction-context-propagation) \| Set a specific [evaluation context](/docs/reference/concepts/evaluation-context) for a transaction (e.g. an HTTP request or a thread) \|
		\| ✅ \| [Extending](#extending) \| Extend OpenFeature with custom providers and hooks. \|
		\| ✅ \| [Providers](#providers) \| Integrate with a commercial, open source, or in-house feature management tool. \|
		\| ✅ \| [Targeting](#targeting) \| Contextually-aware flag evaluation using [evaluation context](/docs/reference/concepts/evaluation-context). \|
		\| ✅ \| [Hooks](#hooks) \| Add functionality to various stages of the flag evaluation life-cycle. \|
		\| ✅ \| [Logging](#logging) \| Integrate with popular logging packages. \|
		\| ✅ \| [Domains](#domains) \| Logically bind clients with providers. \|
		\| ✅ \| [Eventing](#eventing) \| React to state changes in the provider or flag management system. \|
		\| ✅ \| [Transaction Context Propagation](#transaction-context-propagation) \| Set a specific [evaluation context](/docs/reference/concepts/evaluation-context) for a transaction (e.g. an HTTP request or a thread) \|
		\| ✅ \| [Tracking](#tracking) \| Associate user actions with feature flag evaluations, particularly for A/B testing. \|
		\| ✅ \| [Shutdown](#shutdown) \| Gracefully clean up a provider during application shutdown. \|
		\| ✅ \| [Extending](#extending) \| Extend OpenFeature with custom providers and hooks. \|

		@@ -295,2 +296,17 @@ <sub>Implemented: ✅ \| In-progress: ⚠️ \| Not implemented yet: ❌</sub>

		### Tracking

		The tracking API allows you to use OpenFeature abstractions and objects to associate user actions with feature flag evaluations.
		This is essential for robust experimentation powered by feature flags.
		For example, a flag enhancing the appearance of a UI component might drive user engagement to a new feature; to test this hypothesis, telemetry collected by a [hook](#hooks) or [provider](#providers) can be associated with telemetry reported in the client's `track` function.

		```ts
		// flag is evaluated
		await client.getBooleanValue('new-feature', false);

		// new feature is used and track function is called recording the usage
		useNewFeature();
		client.track('new-feature-used');
		```

		### Shutdown
		@@ -297,0 +313,0 @@

@openfeature/server-sdk - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics