@openfeature/server-sdk 1.6.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +201 -0
- package/README.md +315 -0
- package/dist/cjs/index.js +1055 -0
- package/dist/cjs/index.js.map +7 -0
- package/dist/esm/index.js +994 -0
- package/dist/esm/index.js.map +7 -0
- package/dist/esm/package.json +3 -0
- package/dist/types.d.ts +923 -0
- package/package.json +57 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,315 @@
|
|
|
1
|
+
<!-- markdownlint-disable MD033 -->
|
|
2
|
+
<!-- x-hide-in-docs-start -->
|
|
3
|
+
<p align="center">
|
|
4
|
+
<picture>
|
|
5
|
+
<source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/open-feature/community/0e23508c163a6a1ac8c0ced3e4bd78faafe627c7/assets/logo/horizontal/white/openfeature-horizontal-white.svg" />
|
|
6
|
+
<img align="center" alt="OpenFeature Logo" src="https://raw.githubusercontent.com/open-feature/community/0e23508c163a6a1ac8c0ced3e4bd78faafe627c7/assets/logo/horizontal/black/openfeature-horizontal-black.svg" />
|
|
7
|
+
</picture>
|
|
8
|
+
</p>
|
|
9
|
+
|
|
10
|
+
<h2 align="center">OpenFeature Node.js SDK</h2>
|
|
11
|
+
|
|
12
|
+
<!-- x-hide-in-docs-end -->
|
|
13
|
+
<!-- The 'github-badges' class is used in the docs -->
|
|
14
|
+
<p align="center" class="github-badges">
|
|
15
|
+
<a href="https://github.com/open-feature/spec/tree/v0.7.0">
|
|
16
|
+
<img alt="Specification" src="https://img.shields.io/static/v1?label=specification&message=v0.7.0&color=yellow&style=for-the-badge" />
|
|
17
|
+
</a>
|
|
18
|
+
<!-- x-release-please-start-version -->
|
|
19
|
+
<a href="https://github.com/open-feature/js-sdk/releases/tag/js-sdk-v1.6.2">
|
|
20
|
+
<img alt="Release" src="https://img.shields.io/static/v1?label=release&message=v1.6.2&color=blue&style=for-the-badge" />
|
|
21
|
+
</a>
|
|
22
|
+
<!-- x-release-please-end -->
|
|
23
|
+
<br/>
|
|
24
|
+
<a href="https://open-feature.github.io/js-sdk/modules/OpenFeature_JS_SDK.html">
|
|
25
|
+
<img alt="API Reference" src="https://img.shields.io/badge/reference-teal?logo=javascript&logoColor=white" />
|
|
26
|
+
</a>
|
|
27
|
+
<a href="https://www.npmjs.com/package/@openfeature/js-sdk">
|
|
28
|
+
<img alt="NPM Download" src="https://img.shields.io/npm/dm/%40openfeature%2Fjs-sdk" />
|
|
29
|
+
</a>
|
|
30
|
+
<a href="https://codecov.io/gh/open-feature/js-sdk">
|
|
31
|
+
<img alt="codecov" src="https://codecov.io/gh/open-feature/js-sdk/branch/main/graph/badge.svg?token=3DC5XOEHMY" />
|
|
32
|
+
</a>
|
|
33
|
+
<a href="https://bestpractices.coreinfrastructure.org/projects/6594">
|
|
34
|
+
<img alt="CII Best Practices" src="https://bestpractices.coreinfrastructure.org/projects/6594/badge" />
|
|
35
|
+
</a>
|
|
36
|
+
</p>
|
|
37
|
+
<!-- x-hide-in-docs-start -->
|
|
38
|
+
|
|
39
|
+
[OpenFeature](https://openfeature.dev) is an open standard that provides a vendor-agnostic, community-driven API for feature flagging that works with your favorite feature flag management tool.
|
|
40
|
+
|
|
41
|
+
<!-- x-hide-in-docs-end -->
|
|
42
|
+
|
|
43
|
+
## 🚀 Quick start
|
|
44
|
+
|
|
45
|
+
### Requirements
|
|
46
|
+
|
|
47
|
+
- Node.js version 16+
|
|
48
|
+
|
|
49
|
+
### Install
|
|
50
|
+
|
|
51
|
+
#### npm
|
|
52
|
+
|
|
53
|
+
```sh
|
|
54
|
+
npm install --save @openfeature/js-sdk
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
#### yarn
|
|
58
|
+
|
|
59
|
+
```sh
|
|
60
|
+
yarn add @openfeature/js-sdk
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
### Usage
|
|
64
|
+
|
|
65
|
+
```ts
|
|
66
|
+
import { OpenFeature } from '@openfeature/js-sdk';
|
|
67
|
+
|
|
68
|
+
// Register your feature flag provider
|
|
69
|
+
OpenFeature.setProvider(new YourProviderOfChoice());
|
|
70
|
+
|
|
71
|
+
// create a new client
|
|
72
|
+
const client = OpenFeature.getClient();
|
|
73
|
+
|
|
74
|
+
// Evaluate your feature flag
|
|
75
|
+
const v2Enabled = await client.getBooleanValue('v2_enabled', false);
|
|
76
|
+
|
|
77
|
+
if (v2Enabled) {
|
|
78
|
+
console.log("v2 is enabled");
|
|
79
|
+
}
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
### API Reference
|
|
83
|
+
|
|
84
|
+
See [here](https://open-feature.github.io/js-sdk/modules/OpenFeature_JS_SDK.html) for the complete API documentation.
|
|
85
|
+
|
|
86
|
+
## 🌟 Features
|
|
87
|
+
|
|
88
|
+
| Status | Features | Description |
|
|
89
|
+
| ------ | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
|
|
90
|
+
| ✅ | [Providers](#providers) | Integrate with a commercial, open source, or in-house feature management tool. |
|
|
91
|
+
| ✅ | [Targeting](#targeting) | Contextually-aware flag evaluation using [evaluation context](https://openfeature.dev/docs/reference/concepts/evaluation-context). |
|
|
92
|
+
| ✅ | [Hooks](#hooks) | Add functionality to various stages of the flag evaluation life-cycle. |
|
|
93
|
+
| ✅ | [Logging](#logging) | Integrate with popular logging packages. |
|
|
94
|
+
| ✅ | [Named clients](#named-clients) | Utilize multiple providers in a single application. |
|
|
95
|
+
| ✅ | [Eventing](#eventing) | React to state changes in the provider or flag management system. |
|
|
96
|
+
| ✅ | [Shutdown](#shutdown) | Gracefully clean up a provider during application shutdown. |
|
|
97
|
+
| ✅ | [Extending](#extending) | Extend OpenFeature with custom providers and hooks. |
|
|
98
|
+
|
|
99
|
+
<sub>Implemented: ✅ | In-progress: ⚠️ | Not implemented yet: ❌</sub>
|
|
100
|
+
|
|
101
|
+
### Providers
|
|
102
|
+
|
|
103
|
+
[Providers](https://openfeature.dev/docs/reference/concepts/provider) are an abstraction between a flag management system and the OpenFeature SDK.
|
|
104
|
+
Look [here](https://openfeature.dev/ecosystem/?instant_search%5BrefinementList%5D%5Btype%5D%5B0%5D=Provider&instant_search%5BrefinementList%5D%5Bcategory%5D%5B0%5D=Server-side&instant_search%5BrefinementList%5D%5Btechnology%5D%5B0%5D=JavaScript) for a complete list of available providers.
|
|
105
|
+
If the provider you're looking for hasn't been created yet, see the [develop a provider](#develop-a-provider) section to learn how to build it yourself.
|
|
106
|
+
|
|
107
|
+
Once you've added a provider as a dependency, it can be registered with OpenFeature like this:
|
|
108
|
+
|
|
109
|
+
```ts
|
|
110
|
+
OpenFeature.setProvider(new MyProvider())
|
|
111
|
+
```
|
|
112
|
+
|
|
113
|
+
In some situations, it may be beneficial to register multiple providers in the same application.
|
|
114
|
+
This is possible using [named clients](#named-clients), which is covered in more details below.
|
|
115
|
+
|
|
116
|
+
### Targeting
|
|
117
|
+
|
|
118
|
+
Sometimes, the value of a flag must consider some dynamic criteria about the application or user, such as the user's location, IP, email address, or the server's location.
|
|
119
|
+
In OpenFeature, we refer to this as [targeting](https://openfeature.dev/specification/glossary#targeting).
|
|
120
|
+
If the flag management system you're using supports targeting, you can provide the input data using the [evaluation context](https://openfeature.dev/docs/reference/concepts/evaluation-context).
|
|
121
|
+
|
|
122
|
+
```ts
|
|
123
|
+
// set a value to the global context
|
|
124
|
+
OpenFeature.setContext({ region: "us-east-1" });
|
|
125
|
+
|
|
126
|
+
// set a value to the client context
|
|
127
|
+
const client = OpenFeature.getClient();
|
|
128
|
+
client.setContext({ version: process.env.APP_VERSION });
|
|
129
|
+
|
|
130
|
+
// set a value to the invocation context
|
|
131
|
+
const requestContext = {
|
|
132
|
+
targetingKey: req.session.id,
|
|
133
|
+
email: req.session.email,
|
|
134
|
+
product: req.productId
|
|
135
|
+
};
|
|
136
|
+
|
|
137
|
+
const boolValue = await client.getBooleanValue('some-flag', false, requestContext);
|
|
138
|
+
```
|
|
139
|
+
|
|
140
|
+
### Hooks
|
|
141
|
+
|
|
142
|
+
[Hooks](https://openfeature.dev/docs/reference/concepts/hooks) allow for custom logic to be added at well-defined points of the flag evaluation life-cycle
|
|
143
|
+
Look [here](https://openfeature.dev/ecosystem/?instant_search%5BrefinementList%5D%5Btype%5D%5B0%5D=Hook&instant_search%5BrefinementList%5D%5Bcategory%5D%5B0%5D=Server-side&instant_search%5BrefinementList%5D%5Btechnology%5D%5B0%5D=JavaScript) for a complete list of available hooks.
|
|
144
|
+
If the hook you're looking for hasn't been created yet, see the [develop a hook](#develop-a-hook) section to learn how to build it yourself.
|
|
145
|
+
|
|
146
|
+
Once you've added a hook as a dependency, it can be registered at the global, client, or flag invocation level.
|
|
147
|
+
|
|
148
|
+
```ts
|
|
149
|
+
import { OpenFeature } from "@openfeature/js-sdk";
|
|
150
|
+
|
|
151
|
+
// add a hook globally, to run on all evaluations
|
|
152
|
+
OpenFeature.addHooks(new ExampleGlobalHook());
|
|
153
|
+
|
|
154
|
+
// add a hook on this client, to run on all evaluations made by this client
|
|
155
|
+
const client = OpenFeature.getClient();
|
|
156
|
+
client.addHooks(new ExampleClientHook());
|
|
157
|
+
|
|
158
|
+
// add a hook for this evaluation only
|
|
159
|
+
const boolValue = await client.getBooleanValue("bool-flag", false, { hooks: [new ExampleHook()]});
|
|
160
|
+
```
|
|
161
|
+
|
|
162
|
+
### Logging
|
|
163
|
+
|
|
164
|
+
The JS SDK will log warning and errors to the console by default.
|
|
165
|
+
This behavior can be overridden by passing a custom logger either globally or per client.
|
|
166
|
+
A custom logger must implement the [Logger interface](../shared/src/logger/logger.ts).
|
|
167
|
+
|
|
168
|
+
```ts
|
|
169
|
+
import type { Logger } from "@openfeature/js-sdk";
|
|
170
|
+
|
|
171
|
+
// The logger can be anything that conforms with the Logger interface
|
|
172
|
+
const logger: Logger = console;
|
|
173
|
+
|
|
174
|
+
// Sets a global logger
|
|
175
|
+
OpenFeature.setLogger(logger);
|
|
176
|
+
|
|
177
|
+
// Sets a client logger
|
|
178
|
+
const client = OpenFeature.getClient();
|
|
179
|
+
client.setLogger(logger);
|
|
180
|
+
```
|
|
181
|
+
|
|
182
|
+
### Named clients
|
|
183
|
+
|
|
184
|
+
Clients can be given a name.
|
|
185
|
+
A name is a logical identifier which can be used to associate clients with a particular provider.
|
|
186
|
+
If a name has no associated provider, the global provider is used.
|
|
187
|
+
|
|
188
|
+
```ts
|
|
189
|
+
import { OpenFeature, InMemoryProvider } from "@openfeature/js-sdk";
|
|
190
|
+
|
|
191
|
+
const myFlags = {
|
|
192
|
+
'v2_enabled': {
|
|
193
|
+
variants: {
|
|
194
|
+
on: true,
|
|
195
|
+
off: false
|
|
196
|
+
},
|
|
197
|
+
disabled: false,
|
|
198
|
+
defaultVariant: "on"
|
|
199
|
+
}
|
|
200
|
+
};
|
|
201
|
+
|
|
202
|
+
// Registering the default provider
|
|
203
|
+
OpenFeature.setProvider(InMemoryProvider(myFlags));
|
|
204
|
+
// Registering a named provider
|
|
205
|
+
OpenFeature.setProvider("otherClient", new InMemoryProvider(someOtherFlags));
|
|
206
|
+
|
|
207
|
+
// A Client backed by default provider
|
|
208
|
+
const clientWithDefault = OpenFeature.getClient();
|
|
209
|
+
// A Client backed by NewCachedProvider
|
|
210
|
+
const clientForCache = OpenFeature.getClient("otherClient");
|
|
211
|
+
```
|
|
212
|
+
|
|
213
|
+
### Eventing
|
|
214
|
+
|
|
215
|
+
Events allow you to react to state changes in the provider or underlying flag management system, such as flag definition changes, provider readiness, or error conditions.
|
|
216
|
+
Initialization events (`PROVIDER_READY` on success, `PROVIDER_ERROR` on failure) are dispatched for every provider.
|
|
217
|
+
Some providers support additional events, such as `PROVIDER_CONFIGURATION_CHANGED`.
|
|
218
|
+
|
|
219
|
+
Please refer to the documentation of the provider you're using to see what events are supported.
|
|
220
|
+
|
|
221
|
+
```ts
|
|
222
|
+
import { OpenFeature, ProviderEvents } from '@openfeature/js-sdk';
|
|
223
|
+
|
|
224
|
+
// OpenFeature API
|
|
225
|
+
OpenFeature.addHandler(ProviderEvents.Ready, (eventDetails) => {
|
|
226
|
+
console.log(`Ready event from: ${eventDetails?.clientName}:`, eventDetails);
|
|
227
|
+
});
|
|
228
|
+
|
|
229
|
+
// Specific client
|
|
230
|
+
const client = OpenFeature.getClient();
|
|
231
|
+
client.addHandler(ProviderEvents.Error, (eventDetails) => {
|
|
232
|
+
console.log(`Error event from: ${eventDetails?.clientName}:`, eventDetails);
|
|
233
|
+
});
|
|
234
|
+
```
|
|
235
|
+
|
|
236
|
+
### Shutdown
|
|
237
|
+
|
|
238
|
+
The OpenFeature API provides a close function to perform a cleanup of all registered providers.
|
|
239
|
+
This should only be called when your application is in the process of shutting down.
|
|
240
|
+
|
|
241
|
+
```ts
|
|
242
|
+
import { OpenFeature } from '@openfeature/js-sdk';
|
|
243
|
+
|
|
244
|
+
await OpenFeature.close()
|
|
245
|
+
```
|
|
246
|
+
|
|
247
|
+
## Extending
|
|
248
|
+
|
|
249
|
+
### Develop a provider
|
|
250
|
+
|
|
251
|
+
To develop a provider, you need to create a new project and include the OpenFeature SDK as a dependency.
|
|
252
|
+
This can be a new repository or included in [the existing contrib repository](https://github.com/open-feature/js-sdk-contrib) available under the OpenFeature organization.
|
|
253
|
+
You’ll then need to write the provider by implementing the [Provider interface](./src/provider/provider.ts) exported by the OpenFeature SDK.
|
|
254
|
+
|
|
255
|
+
```ts
|
|
256
|
+
import { JsonValue, Provider, ResolutionDetails } from '@openfeature/js-sdk';
|
|
257
|
+
|
|
258
|
+
// implement the provider interface
|
|
259
|
+
class MyProvider implements Provider {
|
|
260
|
+
|
|
261
|
+
readonly metadata = {
|
|
262
|
+
name: 'My Provider',
|
|
263
|
+
} as const;
|
|
264
|
+
|
|
265
|
+
// Optional provider managed hooks
|
|
266
|
+
hooks?: Hook<FlagValue>[];
|
|
267
|
+
|
|
268
|
+
resolveBooleanEvaluation(flagKey: string, defaultValue: boolean, context: EvaluationContext, logger: Logger): Promise<ResolutionDetails<boolean>> {
|
|
269
|
+
// code to evaluate a boolean
|
|
270
|
+
}
|
|
271
|
+
|
|
272
|
+
resolveStringEvaluation(flagKey: string, defaultValue: string, context: EvaluationContext, logger: Logger): Promise<ResolutionDetails<string>> {
|
|
273
|
+
// code to evaluate a string
|
|
274
|
+
}
|
|
275
|
+
|
|
276
|
+
resolveNumberEvaluation(flagKey: string, defaultValue: number, context: EvaluationContext, logger: Logger): Promise<ResolutionDetails<number>> {
|
|
277
|
+
// code to evaluate a number
|
|
278
|
+
}
|
|
279
|
+
|
|
280
|
+
resolveObjectEvaluation<T extends JsonValue>(flagKey: string, defaultValue: T, context: EvaluationContext, logger: Logger): Promise<ResolutionDetails<T>> {
|
|
281
|
+
// code to evaluate an object
|
|
282
|
+
}
|
|
283
|
+
|
|
284
|
+
status?: ProviderStatus | undefined;
|
|
285
|
+
events?: OpenFeatureEventEmitter | undefined;
|
|
286
|
+
|
|
287
|
+
initialize?(context?: EvaluationContext | undefined): Promise<void> {
|
|
288
|
+
// code to initialize your provider
|
|
289
|
+
}
|
|
290
|
+
|
|
291
|
+
onClose?(): Promise<void> {
|
|
292
|
+
// code to shut down your provider
|
|
293
|
+
}
|
|
294
|
+
}
|
|
295
|
+
```
|
|
296
|
+
|
|
297
|
+
> Built a new provider? [Let us know](https://github.com/open-feature/openfeature.dev/issues/new?assignees=&labels=provider&projects=&template=document-provider.yaml&title=%5BProvider%5D%3A+) so we can add it to the docs!
|
|
298
|
+
|
|
299
|
+
### Develop a hook
|
|
300
|
+
|
|
301
|
+
To develop a hook, you need to create a new project and include the OpenFeature SDK as a dependency.
|
|
302
|
+
This can be a new repository or included in [the existing contrib repository](https://github.com/open-feature/js-sdk-contrib) available under the OpenFeature organization.
|
|
303
|
+
Implement your own hook by conforming to the [Hook interface](../shared/src/hooks/hook.ts).
|
|
304
|
+
|
|
305
|
+
```ts
|
|
306
|
+
import type { Hook, HookContext, EvaluationDetails, FlagValue } from "@openfeature/js-sdk";
|
|
307
|
+
|
|
308
|
+
export class MyHook implements Hook {
|
|
309
|
+
after(hookContext: HookContext, evaluationDetails: EvaluationDetails<FlagValue>) {
|
|
310
|
+
// code that runs when there's an error during a flag evaluation
|
|
311
|
+
}
|
|
312
|
+
}
|
|
313
|
+
```
|
|
314
|
+
|
|
315
|
+
> Built a new hook? [Let us know](https://github.com/open-feature/openfeature.dev/issues/new?assignees=&labels=hook&projects=&template=document-hook.yaml&title=%5BHook%5D%3A+) so we can add it to the docs!
|