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

vexapp-sdk

v0.1.3

Published

React SDK for Vex Flags: feature toggles from the Vex dashboard via POST /api/flags

Readme

vexapp-sdk

React SDK for Vex Flags: load feature flag values from the Vex API (POST /api/flags) using your app's API key.

Requirements

  • React 19 and React DOM 19 (peer dependencies)

Allowed URLs

In the dashboard, each API key has an allowed URL list. The browser sends an Origin (or Referer) on POST /api/flags. The API rejects the request unless that origin matches one of your listed URLs (scheme + host + port). Add every origin you load the app from (production, preview, local dev).

403 Forbidden on POST /api/flags

Check the JSON body reason on the response:

| reason | What to fix | | ---------------------- | ----------- | | vex_flags_disabled | Enable Vex Flags for this app in the dashboard (purchase/add-on). | | missing_origin | The request had no Origin or Referer (common with server-side fetch, curl, or non-browser clients). Call the API from the browser, or ensure your dev server origin is sent. | | origin_not_allowed | Add your page’s exact origin to the key’s allowed URLs (e.g. http://localhost:5173 if that is where the app runs). |

The browser console may still log failed network requests for 403s; that comes from DevTools, not the SDK. The provider debounces flag registration so many <VexFlag> components do not each trigger their own immediate request.

Install

bun add vexapp-sdk
npm install vexapp-sdk

Usage

Wrap your app (or a subtree) with VexProvider, passing your API key and, for local development, baseUrl pointing at the Vex API origin (not your Vite dev server).

import { VexFlag, VexProvider } from "vexapp-sdk";

export function App() {
  return (
    <VexProvider
      apiKey={import.meta.env.VITE_VEX_API_KEY}
      baseUrl={import.meta.env.VITE_VEX_API_URL}
    >
      <Main />
    </VexProvider>
  );
}

Use VexFlag with a name and default when the API is unavailable:

<VexFlag name="my-flag" defaultEnabled={false}>
  {(enabled) => (enabled ? <NewFeature /> : <LegacyFeature />)}
</VexFlag>

If you omit baseUrl, the SDK uses the production API host https://vexapp.io.

API surface

| Export | Role | | ------------------ | ------------------------------------------------- | | VexProvider | Context provider; fetches and caches flags | | VexFlag | Declares a flag and renders from remote/default | | useVexFlags | Low-level context hook (nullable) | | fetchFlags | Imperative POST /api/flags helper | | resolveFlagValue | Pure merge of remote boolean vs default |

Docs

Product and dashboard docs: vexapp.io