> For the complete documentation index, see [llms.txt](https://docs.winga.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.winga.me/sdks/nextjs.md).

# @winga/next (Coming soon)

`@winga/next` adds server-side flag evaluation and Edge Runtime middleware support for the Next.js App Router. **It ships in Phase 2** (Starter tier and above) and is not available yet.

***

### Use @winga/js today

In the meantime, evaluate flags with [`@winga/js`](/sdks/javascript.md) inside `'use client'` components, wired through the [`@winga/react`](/sdks/react.md) provider and hooks. That covers client-side flag reads in any Next.js app today.

For server-only reads before the adapter ships, call the [Evaluation API](/api-reference/evaluation-api.md) directly from a Server Component or Route Handler.

***

### What's coming

When `@winga/next` lands, it will add:

* Server Component helpers for reading flags during render.
* Edge Runtime middleware for routing and rewrites based on flag state.

> **Note:** The dashboard's **SDK Setup** section shows a disabled **Next.js (Coming soon)** target for the same reason — both surfaces tell the same Phase 2 story. Pick **JS / TS** or **React** there for now.