@spotify-confidence/openfeature-server-provider-local 0.0.0 → 0.1.0

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/CHANGELOG.md ADDED
@@ -0,0 +1,18 @@
1
+ # Changelog
2
+
3
+ ## 0.1.0 (2025-10-24)
4
+
5
+
6
+ ### Features
7
+
8
+ * js local resolver ([#32](https://github.com/spotify/confidence-resolver-rust/issues/32)) ([58893d6](https://github.com/spotify/confidence-resolver-rust/commit/58893d6610b56b5aa6a6250db9e9bb1af506497f))
9
+ * **js:** add sticky assignment support through remote resolver fallback ([#48](https://github.com/spotify/confidence-resolver-rust/issues/48)) ([baeff3e](https://github.com/spotify/confidence-resolver-rust/commit/baeff3ec39a084615012d961997949748285ac57))
10
+
11
+
12
+ ### Bug Fixes
13
+
14
+ * **js:** correct current time ([#67](https://github.com/spotify/confidence-resolver-rust/issues/67)) ([260f5e3](https://github.com/spotify/confidence-resolver-rust/commit/260f5e3c937dad99e09db1795c6036f0647514c7))
15
+
16
+ ## 0.0.0 (Initial Version)
17
+
18
+ * Initial setup for release-please tracking
package/LICENSE ADDED
@@ -0,0 +1,202 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright [yyyy] [name of copyright owner]
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
package/README.md ADDED
@@ -0,0 +1,184 @@
1
+ ## @spotify-confidence/openfeature-server-provider-local
2
+
3
+ OpenFeature provider for the Spotify Confidence resolver (local mode, powered by WebAssembly). It periodically fetches resolver state, evaluates flags locally, and flushes evaluation logs to the Confidence backend.
4
+
5
+ ### Features
6
+ - Local flag evaluation via WASM (no per-eval network calls)
7
+ - Automatic state refresh and batched flag log flushing
8
+ - Pluggable `fetch` with retries, timeouts and routing
9
+ - Optional logging using `debug`
10
+
11
+ ### Requirements
12
+ - Node.js 18+ (built-in `fetch`) or provide a compatible `fetch`
13
+ - WebAssembly support (Node 18+/modern browsers)
14
+
15
+ ---
16
+
17
+ ## Installation
18
+
19
+ ```bash
20
+ yarn add @spotify-confidence/openfeature-server-provider-local
21
+
22
+ # Optional: enable logs by installing the peer dependency
23
+ yarn add debug
24
+ ```
25
+
26
+ Notes:
27
+ - `debug` is an optional peer. Install it if you want logs. Without it, logging is a no-op.
28
+ - Types and bundling are ESM-first; Node is supported, and a browser build is provided for modern bundlers.
29
+
30
+ ---
31
+
32
+ ## Quick start (Node)
33
+
34
+ ```ts
35
+ import { OpenFeature } from '@openfeature/server-sdk';
36
+ import { createConfidenceServerProvider } from '@spotify-confidence/openfeature-server-provider-local';
37
+
38
+ const provider = createConfidenceServerProvider({
39
+ flagClientSecret: process.env.CONFIDENCE_FLAG_CLIENT_SECRET!,
40
+ apiClientId: process.env.CONFIDENCE_API_CLIENT_ID!,
41
+ apiClientSecret: process.env.CONFIDENCE_API_CLIENT_SECRET!,
42
+ // initializeTimeout?: number
43
+ // flushInterval?: number
44
+ // fetch?: typeof fetch (Node <18 or custom transport)
45
+ });
46
+
47
+ // Wait for the provider to be ready (fetches initial resolver state)
48
+ await OpenFeature.setProviderAndWait(provider);
49
+
50
+ const client = OpenFeature.getClient();
51
+
52
+ // Evaluate a boolean flag
53
+ const details = await client.getBooleanDetails('my-flag', false, { targetingKey: 'user-123' });
54
+ console.log(details.value, details.reason);
55
+
56
+ // Evaluate a nested value from an object flag using dot-path
57
+ // e.g. flag key "experiments" with payload { groupA: { ratio: 0.5 } }
58
+ const ratio = await client.getNumberValue('experiments.groupA.ratio', 0, { targetingKey: 'user-123' });
59
+
60
+ // On shutdown, flush any pending logs
61
+ await provider.onClose();
62
+ ```
63
+
64
+ ---
65
+
66
+ ## Options
67
+
68
+ - `flagClientSecret` (string, required): The flag client secret used during evaluation.
69
+ - `apiClientId` (string, required): OAuth client ID for Confidence IAM.
70
+ - `apiClientSecret` (string, required): OAuth client secret for Confidence IAM.
71
+ - `initializeTimeout` (number, optional): Max ms to wait for initial state fetch. Defaults to 30_000.
72
+ - `flushInterval` (number, optional): Interval in ms for sending evaluation logs. Defaults to 10_000.
73
+ - `fetch` (optional): Custom `fetch` implementation. Required for Node < 18; for Node 18+ you can omit.
74
+
75
+ The provider periodically:
76
+ - Refreshes resolver state (default every 30s)
77
+ - Flushes flag evaluation logs to the backend
78
+
79
+ ---
80
+
81
+ ## Sticky Assignments
82
+
83
+ Confidence supports "sticky" flag assignments to ensure users receive consistent variant assignments even when their context changes or flag configurations are updated. This SDK falls back to a cloud resolve in these cases.
84
+
85
+ > **ℹ️ Latency Considerations**
86
+ >
87
+ > When a sticky assignment is needed, the provider makes a **network call to Confidence's cloud resolvers**. This introduces additional latency (typically 50-200ms depending on your location) compared to local WASM evaluation.
88
+ >
89
+ > **Coming soon**: We're developing support for custom materialization storage (Redis, database, etc.) that will eliminate this network call and keep evaluation latency consistently low.
90
+
91
+ ### How it works
92
+
93
+ When a flag is evaluated for a user, Confidence creates a "materialization" - a snapshot of which variant that user was assigned. On subsequent evaluations, the same variant is returned even if:
94
+ - The user's context attributes change (e.g., different country, device type)
95
+ - The flag's targeting rules are modified
96
+ - New assignments are paused
97
+
98
+ ### Implementation
99
+
100
+ The provider uses a **remote resolver fallback** for sticky assignments:
101
+ - First, the local WASM resolver attempts to resolve the flag
102
+ - If sticky assignment data is needed, the provider makes a network call to Confidence's cloud resolvers
103
+ - Materializations are stored on Confidence servers with a **90-day TTL** (automatically renewed on access)
104
+ - No local storage or database setup required
105
+
106
+ ### Benefits
107
+
108
+ - **Zero configuration**: Works out of the box with no additional setup
109
+ - **Managed storage**: Confidence handles all storage, TTL, and consistency
110
+ - **Automatic renewal**: TTL is refreshed on each access
111
+ - **Global availability**: Materializations are available across all your services
112
+
113
+ ### Coming Soon: Custom Materialization Storage
114
+
115
+ We're working on support for connecting your own materialization storage repository (Redis, database, file system, etc.) to eliminate network calls for sticky assignments and have full control over storage. This feature is currently in development.
116
+
117
+ ---
118
+
119
+ ## Logging (optional)
120
+
121
+ Logging uses the `debug` library if present; otherwise, all log calls are no-ops.
122
+
123
+ Namespaces:
124
+ - Core: `cnfd:*`
125
+ - Fetch/middleware: `cnfd:fetch:*` (e.g. retries, auth renewals, request summaries)
126
+
127
+ Enable logs:
128
+
129
+ - Node:
130
+ ```bash
131
+ DEBUG=cnfd:* node app.js
132
+ # or narrower
133
+ DEBUG=cnfd:info,cnfd:error,cnfd:fetch:* node app.js
134
+ ```
135
+
136
+ - Browser (in DevTools console):
137
+ ```js
138
+ localStorage.debug = 'cnfd:*';
139
+ ```
140
+
141
+ Install `debug` if you haven’t:
142
+
143
+ ```bash
144
+ yarn add debug
145
+ ```
146
+
147
+ ---
148
+
149
+ ## WebAssembly asset notes
150
+
151
+ - Node: the WASM (`confidence_resolver.wasm`) is resolved from the installed package automatically; no extra config needed.
152
+ - Browser: the ESM build resolves the WASM via `new URL('confidence_resolver.wasm', import.meta.url)` so modern bundlers (Vite/Rollup/Webpack 5 asset modules) will include it. If your bundler does not, configure it to treat the `.wasm` file as a static asset.
153
+
154
+ ---
155
+
156
+ ## Using in browsers
157
+
158
+ The package exports a browser ESM build that compiles the WASM via streaming and uses the global `fetch`. Integrate it with your OpenFeature SDK variant for the web similarly to Node, then register the provider before evaluation. Credentials must be available to the runtime (e.g. through your app’s configuration layer).
159
+
160
+ ---
161
+
162
+ ## Testing
163
+
164
+ - You can inject a custom `fetch` via the `fetch` option to stub network behavior in tests.
165
+ - The provider batches logs; call `await provider.onClose()` in tests to flush them deterministically.
166
+
167
+ ---
168
+
169
+ ## Troubleshooting
170
+
171
+ - Provider stuck in NOT_READY/ERROR:
172
+ - Verify `apiClientId`/`apiClientSecret` and `flagClientSecret` are correct.
173
+ - Ensure outbound access to Confidence endpoints and GCS.
174
+ - Enable `DEBUG=cnfd:*` for more detail.
175
+
176
+ - No logs appear:
177
+ - Install `debug` and enable the appropriate namespaces.
178
+ - Check that your environment variable/`localStorage.debug` is set before your app initializes the provider.
179
+
180
+ ---
181
+
182
+ ## License
183
+
184
+ See the root `LICENSE`.
Binary file
package/package.json CHANGED
@@ -1,10 +1,13 @@
1
1
  {
2
2
  "name": "@spotify-confidence/openfeature-server-provider-local",
3
- "version": "0.0.0",
3
+ "version": "0.1.0",
4
4
  "description": "Spotify Confidence Open Feature provider",
5
5
  "type": "module",
6
6
  "files": [
7
- "dist"
7
+ "dist",
8
+ "README.md",
9
+ "CHANGELOG.md",
10
+ "LICENSE"
8
11
  ],
9
12
  "main": "./dist/index.node.js",
10
13
  "module": "./dist/index.browser.js",
@@ -76,4 +79,4 @@
76
79
  "url": "https://github.com/spotify/confidence-resolver-rust/issues"
77
80
  },
78
81
  "homepage": "https://github.com/spotify/confidence-resolver-rust?tab=readme-ov-file#confidence-rust-flags-resolver"
79
- }
82
+ }