# Flags SDK 4.2.3

- Product: Flags SDK (https://whatsnew.fyi/product/flags-sdk)
- Vendor: Vercel
- Date: 2026-07-24
- Version: 4.2.3
- Original notes: https://github.com/vercel/flags/releases/tag/flags%404.2.3
- Permalink: https://whatsnew.fyi/product/flags-sdk/releases/4.2.3

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **fixed** — Remove @sveltejs/kit from peer dependencies to prevent ERESOLVE errors in non-SvelteKit projects using Vite 7

###### Patch Changes

-   [#442](https://github.com/vercel/flags/pull/442) [`622d56e`](https://github.com/vercel/flags/commit/622d56e608f091a8fbfbda0ee076ea3dcf808e52) Thanks [@dferber90](https://github.com/dferber90)! - Remove `@sveltejs/kit` from peer dependencies. It was declared as an optional peer with a `"*"` range, which caused npm to auto-install the newest `@sveltejs/kit` and drag in its transitive `@sveltejs/vite-plugin-svelte` → `vite` peer chain. In non-SvelteKit projects already on Vite 7 (via Vitest, Storybook, etc.) this produced a hard `ERESOLVE` error requiring `npm install --force`. SvelteKit consumers always have `@sveltejs/kit` installed as the framework, so the `flags/sveltekit` entrypoint continues to resolve it from their own tree.