flagsmith-nodejs - npm Package Versions

v6.0.1 - 2025-04-24

What's Changed

• Remove uses of any in models.ts by @phiggins in #180
• Bump esbuild from 0.14.54 to 0.25.0 by @dependabot in #175
• Bump vite from 5.4.14 to 5.4.18 by @dependabot in #182

New Contributors

• @phiggins made their first contribution in #180

Full Changelog: https://github.com/Flagsmith/flagsmith-nodejs-client/compare/v6.0.0...v6.0.1

[Changes][v6.0.1]

<a id="v6.0.0"></a>

v6.0.0 - 2025-03-24

What's Changed

BREAKING CHANGES

• Flagsmith.environment was removed. Use getEnvironment instead. This returns a Promise, and not a reference to the environment which could be uninitialised.
• onEnvironmentChange handlers can now be invoked with an undefined environment if an error occurred.
• The Flagsmith client now returns an error if initialised with local evaluation enabled but without a server-side SDK key. Previously, it would log an error and continue.

New features

• Added a new requestRetryDelayMilliseconds which controls how long the SDK will wait before retrying any failed HTTP requests. Previously, this was hard-coded to always be 1 second.
• Added a getEnvironment method which returns the SDK's current local environment state as a Promise.

Bug fixes

• getIdentityFlags now uses any provided default flag handler if it fails, instead of just returning an error.
• Setting environmentRefreshInterval to 0 now prevents any environment polling from happening.
• Fixed a bug where if the SDK initially failed to fetch the environment document, then getIdentityFlags would always fail with an error even if the environment was later fetched successfully (https://github.com/Flagsmith/flagsmith-nodejs-client/issues/177).

Full Changelog: https://github.com/Flagsmith/flagsmith-nodejs-client/compare/v5.1.1...v6.0.0

[Changes][v6.0.0]

<a id="v5.1.1"></a>

v5.1.1 - 2025-02-10

What's Changed

• Bump undici from 6.19.8 to 6.21.1 by @dependabot in #170
• Bump vite from 5.4.8 to 5.4.14 by @dependabot in #171
• Bump vitest and @vitest/coverage-v8 by @dependabot in #173

Full Changelog: https://github.com/Flagsmith/flagsmith-nodejs-client/compare/v5.1.0...v5.1.1

[Changes][v5.1.1]

<a id="v5.1.0"></a>

v5.1.0 - 2025-01-20

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: https://github.com/Flagsmith/flagsmith-nodejs-client/compare/v5.0.1...v5.1.0

[Changes][v5.1.0]

<a id="v5.0.1"></a>

v5.0.1 - 2025-01-14

What's Changed

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

Full Changelog: https://github.com/Flagsmith/flagsmith-nodejs-client/compare/v5.0.0...v5.0.1

[Changes][v5.0.1]

<a id="v5.0.0"></a>

v5.0.0 - 2024-11-28

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 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: https://github.com/Flagsmith/flagsmith-nodejs-client/compare/v4.0.0...v5.0.0

[Changes][v5.0.0]

<a id="v4.0.0"></a>

v4.0.0 - 2024-11-07

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: https://github.com/Flagsmith/flagsmith-nodejs-client/compare/v3.3.3...v4.0.0

[Changes][v4.0.0]

<a id="v3.3.3"></a>

v3.3.3 - 2024-07-12

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: https://github.com/Flagsmith/flagsmith-nodejs-client/compare/v3.3.2...v3.3.3

[Changes][v3.3.3]

<a id="v3.3.2"></a>