npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@arlioz/flagship-next

v5.1.0

Published

Official Next.js SDK for FlagShip — SSR-ready feature flags

Downloads

262

Readme


Install

npm install @arlioz/flagship-next @arlioz/flagship

@arlioz/flagship, react, and next are peer dependencies.

Quick Start (App Router)

1. Fetch flags server-side

// app/layout.tsx (Server Component)
import { getFlags } from '@arlioz/flagship-next/server'
import { Providers } from './providers'

export default async function RootLayout({ children }) {
  const flags = await getFlags({
    apiKey: process.env.FLAGSHIP_API_KEY!,
    baseUrl: process.env.FLAGSHIP_API_URL,
  })

  return (
    <html>
      <body>
        <Providers initialFlags={flags}>{children}</Providers>
      </body>
    </html>
  )
}

2. Wrap with provider

// app/providers.tsx
'use client'
import { FlagShipProvider } from '@arlioz/flagship-next'

export function Providers({ children, initialFlags }) {
  return (
    <FlagShipProvider
      apiKey={process.env.NEXT_PUBLIC_FLAGSHIP_API_KEY!}
      initialFlags={initialFlags}
    >
      {children}
    </FlagShipProvider>
  )
}

3. Use flags in components

'use client'
import { useFlag, Feature } from '@arlioz/flagship-next'

function MyComponent() {
  const darkMode = useFlag('dark-mode', false)

  return (
    <>
      {darkMode && <DarkTheme />}
      <Feature flag="beta" fallback={<ComingSoon />}>
        <BetaFeature />
      </Feature>
    </>
  )
}

4. Use flags in Server Components

import { getFlag } from '@arlioz/flagship-next/server'

export default async function Page() {
  const showBeta = await getFlag({ apiKey: process.env.FLAGSHIP_API_KEY! }, 'beta', false)
  return showBeta ? <BetaUI /> : <StableUI />
}

Two Entry Points

| Import | Use in | Description | | ------------------------------ | ----------------- | ---------------------------- | | @arlioz/flagship-next | Client Components | Provider, hooks, <Feature> | | @arlioz/flagship-next/server | Server Components | getFlags(), getFlag() |

API — Client

| Hook / Component | Return | Description | | ----------------------------------- | --------------------- | ------------------------- | | useFlag<T>(key, defaultValue?) | T | Single flag value | | useFlags() | Record<string, any> | All flags | | useFlagShipLoading() | boolean | True during initial fetch | | useFlagShipClient() | FlagShip | Client for imperative use | | <Feature flag children fallback?> | ReactNode | Conditional rendering |

API — Server

| Function | Return | Description | | --------------------------------- | ------------------------------ | -------------------------------- | | getFlags(options) | Promise<Record<string, any>> | Fetch all flags (auto-cleanup) | | getFlag(options, key, default?) | Promise<T> | Fetch single flag (auto-cleanup) | | FlagShipServer | class | Long-lived server client |

SSR Benefits

  • No hydration mismatchinitialFlags ensures server and client render identically
  • No flash of default content — flags are available on first render
  • Client-side polling — flags continue updating after hydration

Compatibility

  • Next.js >= 13.0.0 (App Router + Pages Router)
  • React >= 17.0.0

License

MIT — Arlioz