Upgrading @atlaskit/feature-gate-js-client from 7.x to 8.x
Comparison of the public API of @atlaskit/feature-gate-js-client 7.1.0 and 8.0.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.
Summary
| Removed import paths | 0 |
|---|---|
| Removed exports | 0 |
| Changed signatures | 0 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 0 |
| New exports | 0 |
Removed exports
None detected.
Changed signatures
None detected.
Removed class or interface members
None detected.
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
None detected.
Changelog between these versions
Text published by the package authors, shown as-is.
8.0.0
### Major Changes
- [`67eb7db820b2b`](https://bitbucket.org/atlassian/atlassian-frontend-monorepo/commits/67eb7db820b2b) -
With `includeFfpFlags: true`, `checkGate`, `getExperiment` and `getExperimentValue` serve flags
from the Feature Flag Platform (FFP) as well as Statsig, so flags migrated to FFP keep working
without code changes. Without the option, only Statsig is used, as before. If you initialize with
`initializeFromValues`, also pass the FFP values to serve FFP flags.
- [`67eb7db820b2b`](https://bitbucket.org/atlassian/atlassian-frontend-monorepo/commits/67eb7db820b2b) -
Add `FeatureGates.ffpClient` to read flags that exist only in the Feature Flag Platform (FFP),
available once the client is initialized. Keep reading existing Statsig flags, including ones
being migrated to FFP, with `checkGate`, `getExperiment` and `getExperimentValue`. Its type,
`FfpEvaluationClient`, is exported from `@atlaskit/feature-gate-js-client/ffp/types`.
### Minor Changes
- [`67eb7db820b2b`](https://bitbucket.org/atlassian/atlassian-frontend-monorepo/commits/67eb7db820b2b) -
Add `./eval-flags/*` entry points that expose the `/api/v1/evalFlags` response helpers.
`@atlaskit/feature-gate-fetcher` now uses them instead of its own copy, so products that bundle
both packages ship one implementation.
### Patch Changes
- Updated dependenciesGive your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
Frequently asked questions
What are the breaking changes when upgrading @atlaskit/feature-gate-js-client from 7 to 8?
Between @atlaskit/feature-gate-js-client 7.1.0 and 8.0.0, Vigia found 0 removed exports, 0 changed signatures and 0 removed or changed class or interface members.
What became deprecated in @atlaskit/feature-gate-js-client 8?
0 exports or members are newly marked as deprecated in @atlaskit/feature-gate-js-client 8.0.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/@atlaskit/feature-gate-js-client/upgrade?from=7.1.0&to=8.0.0