Releases: Flagsmith/flagsmith-nodejs-client
v5.1.0
What's Changed
- feat: Allow configuring analytics API endpoint separate from flags API by @rolodato in #168
- ci: Run tests on currently maintained Node LTS versions by @rolodato in #169
Deprecated
The baseApiUrl
constructor argument of AnalyticsProcessor
is now deprecated. Instead, pass the full URL to the analytics endpoint using the analyticsUrl
parameter. This deprecation only affects you if you are manually managing analytics, rather than having the SDK do it for you using the enableAnalytics
option.
Full Changelog: v5.0.1...v5.1.0
v5.0.1
v5.0.0
What's Changed
- fix: Export offline handler types by @rolodato in #166
- feat!: Simplify FlagsmithCache interface by @rolodato in #165
BREAKING CHANGES
The FlagsmithCache
interface has been simplified. In practice, this will not affect most users:
- Removed
has
method - Removed
ttl
parameter fromset
- Changed
set
return type toPromise<void>
- Changed
get
return type toPromise<Flags | undefined>
FlagsmithCache
since 5.0.0: https://www.tsdocs.dev/docs/flagsmith-nodejs/5.0.0/interfaces/FlagsmithCache.html
FlagsmithCache
prior to 5.0.0: https://www.tsdocs.dev/docs/flagsmith-nodejs/4.0.0/interfaces/FlagsmithCache.html
Full Changelog: v4.0.0...v5.0.0
v4.0.0
What's Changed
- feat: Support transient identities and traits by @novakzaballa in #158
- feat!: Custom fetch support, remove node-fetch, ESM+CJS dual build, migrate to vitest, TS fixes, test improvements by @rolodato in #162
- feat!: Remove all uses of CJS, add named Flagsmith export by @rolodato in #163
BREAKING CHANGES
Node.js 18 or later is now required.
Flagsmith
is now a named export and not a default export. This only changes how you import the Flagsmith Node.js SDK and not how you use it.
In 3.x and earlier, Flagsmith
is the default export:
// ES modules
import Flagsmith from 'flagsmith-nodejs'
// CommonJS
const Flagsmith = require('flagsmith-nodejs')
In 4.x, you must use the named export:
// ES modules
import { Flagsmith } from 'flagsmith-nodejs'
// CommonJS
const { Flagsmith } = require('flagsmith-nodejs')
Full Changelog: v3.3.3...v4.0.0
v4.0.0-beta.1
Breaking changes
Node.js >=18 is now required.
New features
flagsmith-nodejs
is now published as both an ES and CommonJS module. This lets you use eitherimport
orrequire
syntax to use this module from your application code- Support transient identities and traits by @novakzaballa in #158
- Support custom
fetch
implementations
Bug fixes
- Use
AbortSignal
to cancel timed outfetch
calls by @AlissonRS in #161 - Fix environment document being fetched twice on startup by @rolodato in #147
Full Changelog: v3.3.3...v4.0.0-beta.1
v3.3.3
What's Changed
- Cancel timeout when it is no longer needed by @wheineman-sunrun in #141
New Contributors
- @wheineman-sunrun made their first contribution in #141
Full Changelog: v3.3.2...v3.3.3
v3.3.2
What's Changed
- fix: handle null traits for regex evaluations by @matthewelwell in #152
Full Changelog: v3.3.1...v3.3.2
v3.3.1
What's Changed
- fix: only flush analytics once if requested concurrently by @rolodato in #148
- fix: error evaluating CONTAINS / NOT_CONTAINS for null traits by @matthewelwell in #150
- Bump version 3.3.1 by @matthewelwell in #151
New Contributors
Full Changelog: v3.3.0...v3.3.1
Version 3.3.0
What's Changed
- feat: Identity overrides in local evaluation mode by @khvn26 in #143
- Bump @babel/traverse from 7.17.3 to 7.23.2 by @dependabot in #137
- chore: export FlagsmithConfig from index by @novakzaballa in #139
- chore: remove examples by @dabeeeenster in #145
New Contributors
Full Changelog: v3.2.0...v3.3.0