Skip to content

Releases: Flagsmith/flagsmith-nodejs-client

v5.1.0

20 Jan 13:40
2d26062
Compare
Choose a tag to compare

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

14 Jan 22:25
d52fbac
Compare
Choose a tag to compare

What's Changed

  • fix: Return 0 as number flag value instead of undefined by @rolodato in #167

Full Changelog: v5.0.0...v5.0.1

v5.0.0

28 Nov 13:21
3d04ec7
Compare
Choose a tag to compare

What's Changed

BREAKING CHANGES

The FlagsmithCache interface has been simplified. In practice, this will not affect most users:

  • Removed has method
  • Removed ttl parameter from set
  • Changed set return type to Promise<void>
  • Changed get return type to Promise<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

07 Nov 13:57
2cc95c7
Compare
Choose a tag to compare

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

08 Oct 21:14
7afadbc
Compare
Choose a tag to compare
v4.0.0-beta.1 Pre-release
Pre-release

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 either import or require 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 out fetch 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

12 Jul 16:16
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.3.2...v3.3.3

v3.3.2

23 May 17:24
ba17b92
Compare
Choose a tag to compare

What's Changed

Full Changelog: v3.3.1...v3.3.2

v3.3.1

08 May 14:36
9cbbbaf
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.3.0...v3.3.1

Version 3.3.0

19 Apr 13:23
ad2127c
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v3.2.0...v3.3.0

Version 3.2.0

25 Oct 15:03
4159bfd
Compare
Choose a tag to compare

What's Changed

Full Changelog: v3.1.1...v3.2.0