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

@optify/config

v1.3.0

Published

Simplifies **configuration driven development**: getting the right configuration options for a process or request using pre-loaded configurations from files (JSON, YAML, etc.) to manage options for feature flags, experiments, or flights.

Downloads

620

Readme

Optify Bindings for Node.js

NPM Version

See the homepage for details about how feature files are combined to build the options to process at runtime.

Usage

import { z } from 'zod'
import { OptionsProvider } from '@optify/config'

const MyConfigSchema = z.object({
  rootString: z.string(),
  myArray: z.array(z.string()),
  myObject: z.object({
    key: z.string(),
    deeper: z.object({
      new: z.string(),
      num: z.number(),
    }),
  }),
}).readonly()

const provider = OptionsProvider.build('<configs folder path>')
const config = provider.getOptions('myConfig', ['feature_A', 'feature_B'], MyConfigSchema)
// config is typed and validated at runtime
console.log(config.rootString)
console.log(config.myObject.deeper.num)

The getOptions method accepts any object with a parse(data: unknown): T method, making it compatible with Zod and other schema validation libraries. This package does not depend on Zod; it only requires the schema to have a parse method. If desired, install Zod (or your preferred validation library) separately in your project:

npm install zod

Using getOptionsJson

If you don't need schema validation, you can use getOptionsJson to get the raw JSON string:

import { OptionsProvider } from '@optify/config'

const provider = OptionsProvider.build('<configs folder path>')
const options = JSON.parse(provider.getOptionsJson('myConfig', ['feature_A', 'feature_B']))
console.log(JSON.stringify(options, null, 2))

Outputs:

{
  "myArray": [
    "item 1",
    "item 2"
  ],
  "myObject": {
    "deeper": {
      "new": "new value",
      "num": 3333
    },
    "key": "val"
  },
  "rootString": "root string same"
}

Multiple directories

import { OptionsProvider } from '@optify/config'

const provider = OptionsProvider.buildFromDirectories(['<configs folder path>', '<another folder path>'])

Development

Use Node >= 22.

corepack enable
yarn install
yarn build:debug
yarn build:ts
yarn test

Testing

Run:

yarn build:debug
yarn build:ts
yarn test

Formatting

JavaScript and TypeScript files use tabs as configured in .editorconfig. Run oxfmt before committing:

yarn fmt

To check for formatting issues, run:

yarn fmt:check

Linting

Run linting before committing:

yarn lint:fix

To check for issues, run:

yarn lint

Rust Formatting

To automatically format the Rust code, run:

cargo fmt

Benchmarking

Run:

rm -rf target config.*.node
yarn build
yarn build:ts
node benchmarks/get_all_options.mjs

Publishing

Use CI.

Some notes:

See https://napi.rs/docs/introduction/getting-started#deep-dive
See https://napi.rs/docs/introduction/simple-package