# @atlaskit/platform-feature-flags

> Platform Feature Flags

Latest version **2.2.0** (published 2026-08-29) · Apache-2.0 license · 0 weekly downloads

## Install

```sh
npm install @atlaskit/platform-feature-flags
pnpm add @atlaskit/platform-feature-flags
yarn add @atlaskit/platform-feature-flags
bun add @atlaskit/platform-feature-flags
```

## Health

**Score 65/100 (B)** — status: active.

Positive: has types; esm support; no vulnerabilities; recently updated; high maintenance score.

Warnings: low downloads.

## Facts

| | |
|---|---|
| Version | 2.2.0 |
| Published | 2026-08-29 |
| First published | 2022-12-08 |
| Weekly downloads | 0 |
| License | Apache-2.0 |
| TypeScript types | bundled |
| Module format | ESM + CommonJS |
| Dependencies | 2 |
| Unpacked size | 30.1 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | Atlassian Pty Ltd |
| Maintainers | atlassianartifactteam |

## Links

- npm: https://www.npmjs.com/package/@atlaskit/platform-feature-flags
- Repository: https://bitbucket.org/atlassian/atlassian-frontend-mirror
- Homepage: https://bitbucket.org/atlassian/atlassian-frontend-mirror#readme
- Issues: https://bitbucket.org/atlassian/atlassian-frontend-mirror/issues
- npm.io page: https://npm.io/package/@atlaskit/platform-feature-flags

## Dependencies (2)

- [@babel/runtime](https://npm.io/package/@babel/runtime.md) ^7.0.0
- [@atlaskit/feature-gate-js-client](https://npm.io/package/@atlaskit/feature-gate-js-client.md) ^6.0.0

## Recent versions

- 2.2.0 (latest) — 2026-08-29
- 0.2.2 (next) — 2023-05-17
- 2.1.1 — 2026-07-23
- 2.1.0 — 2026-07-21
- 2.0.0 — 2026-06-16
- 1.1.3 — 2026-01-23
- 1.1.2 — 2025-09-03
- 1.1.1 — 2025-03-24
- 1.1.0 — 2025-02-18
- 1.0.0 — 2025-02-04
- 0.3.0 — 2024-06-29
- 0.2.6 — 2024-06-28
- 0.2.5 — 2023-11-06
- 0.2.4 — 2023-06-23
- 0.2.3 — 2023-06-20
- … 17 more at https://npm.io/package/@atlaskit/platform-feature-flags/versions

## README

# @atlaskit/platform-feature-flags

Allows usage of feature flags in platform components.

## Registration

Feature flags are required to be registered in their respective package before they will be available in the api.
This is because the types used in this package are dynamically generated based on flags defined in their "package.json".
Definitions can be like so:

```json5
{
  'platform-feature-flags': {
    'flag-name': {
      type: 'boolean',
      // required
    },
  },
}
```

---
_Source: https://npm.io/package/@atlaskit/platform-feature-flags · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._