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

@omniretail/omniflags-react

v1.0.25

Published

OmniFlags React SDK — provider + hooks for feature flags

Downloads

2,757

Readme

@omniretail/omniflags-react

React SDK for OmniFlags.

Installation

npm install @omniretail/omniflags-react

Quick start

Wrap your app with OmniFlagsProvider and use the hooks anywhere below it.

import { OmniFlagsProvider, useFlag } from "@omniretail/omniflags-react";

function App() {
  return (
    <OmniFlagsProvider sdkKey="your-sdk-key">
      <MyApp />
    </OmniFlagsProvider>
  );
}

function MyApp() {
  const darkMode = useFlag("store.dark-mode");
  return <div className={darkMode ? "dark" : "light"}>...</div>;
}

Provider

<OmniFlagsProvider sdkKey="your-sdk-key">
  {children}
</OmniFlagsProvider>

| Prop | Type | Description | |------|------|-------------| | sdkKey | string | Required. SDK key from the OmniFlags dashboard. |

Hooks

useFlag

Evaluates a boolean flag.

const enabled = useFlag("store.show-banner");
const enabled = useFlag("store.show-banner", { customerId: "cust-123" }); // with context
const enabled = useFlag("store.show-banner", undefined, false);            // custom default

useFlagValue

Returns the typed value of a flag.

const theme = useFlagValue<string>("store.theme", "light");
const limit = useFlagValue<number>("store.item-limit", 10);
const theme = useFlagValue<string>("store.theme", "light", { businessId: "biz-456" }); // with context

useFlagVariant

Returns the full evaluation result — value, variant, reason, and which rule matched.

const result = useFlagVariant("store.show-banner");
// result.value, result.variant, result.reason, result.ruleId, result.errorCode

useFlagStatus

Returns the current loading state of the flag client.

const { isFetching, isLoading, origin, error } = useFlagStatus();

| Field | Type | Description | |-------|------|-------------| | isFetching | boolean | A network request is in flight. | | isLoading | boolean | No flags have been loaded yet (first fetch pending). | | origin | FlagOrigin | Where the current flags came from: "NONE", "CACHE", or "SERVER". | | error | Error \| null | The last fetch error, or null. |

function FlagGate({ children }: { children: React.ReactNode }) {
  const { isLoading } = useFlagStatus();
  if (isLoading) return <Spinner />;
  return <>{children}</>;
}

useOmniFlags

Low-level access to the underlying client and ready state.

const { client, ready } = useOmniFlags();

Context

Context is passed per evaluation call — customer, business, branch, country, etc. There is no persistent context state.

function Banner({ customerId, businessId }: Props) {
  const ctx = { customerId, businessId };
  const show = useFlag("store.show-banner", ctx);
  return show ? <Banner /> : null;
}

Flag keys

Keys are namespaced by project: {projectKey}.{flagKey}. Find the full flag key in the OmniFlags dashboard on the flag detail page.

Next.js (App Router)

Add the provider to your root layout. Store the SDK key in .env.local:

NEXT_PUBLIC_OMNIFLAGS_SDK_KEY=your-sdk-key
// app/layout.tsx
import { OmniFlagsProvider } from '@omniretail/omniflags-react'

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html>
      <body>
        <OmniFlagsProvider sdkKey={process.env.NEXT_PUBLIC_OMNIFLAGS_SDK_KEY!}>
          {children}
        </OmniFlagsProvider>
      </body>
    </html>
  )
}

Use hooks inside 'use client' components. Flag evaluation happens on the client after the first fetch, so guard against the initial loading state where needed:

'use client'
import { useFlagValue, useFlagStatus } from '@omniretail/omniflags-react'

export function CheckoutButton() {
  const { isLoading } = useFlagStatus()
  const useNewFlow = useFlagValue('checkout.new-flow', false)

  if (isLoading) return null

  return <button>{useNewFlow ? 'Express checkout' : 'Checkout'}</button>
}

Server Components passed as children into the provider are unaffected — they still run on the server.