# What changed in @openfeature/core

> 4 changes in @openfeature/core 1 from its official release notes, upgrade guides and advisories: 3 new APIs and options. Each one cited. Sources checked 2026-10-18. HTML: https://unstale.sh/npm/@openfeature/core/

To see which of these apply to a repository, run `npx @unstale/cli init` in it.

## @openfeature/core 1

### New APIs and options

- Provider initialization receives the bound domain, and binding is enforced per domain. (1.12.0) — [release notes](https://github.com/open-feature/js-sdk/releases/tag/core-v1.12.0)
- Client metadata now exposes the JavaScript SDK identity. (1.11.0) — [release notes](https://github.com/open-feature/js-sdk/releases/tag/core-v1.11.0)
- Flag keys can now be made type-safe via module augmentation. (1.10.0) — [release notes](https://github.com/open-feature/js-sdk/releases/tag/core-v1.10.0)

### Performance

- Package metadata now declares sideEffects as false, allowing bundlers to treat package files as free of side effects. (1.10.0) — [release notes](https://github.com/open-feature/js-sdk/releases/tag/core-v1.10.0)