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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@prefab-cloud/prefab-cloud-node

v0.4.2

Published

Feature Flags, Live Config, and Dynamic Log Levels

Downloads

3,744

Readme

prefab-cloud-nodejs

Prefab Node.js client


Install the client

npm install @prefab-cloud/prefab-cloud-node or yarn add @prefab-cloud/prefab-cloud-node

Set up a Prefab client.

import { Prefab } from "@prefab-cloud/prefab-cloud-node";

if (!process.env.PREFAB_API_KEY) {
  throw new Error("PREFAB_API_KEY is not set");
}

const prefab = new Prefab({
  apiKey: process.env.PREFAB_API_KEY,
  enableSSE: true,
  enablePolling: true,
});

await prefab.init();

After the init completes you can use

  • prefab.get('some.config.name') returns a raw value
  • prefab.isFeatureEnabled('some.feature.name') returns true or false
  • prefab.shouldLog({loggerName, desiredLevel, defaultLevel, contexts}) returns true or false

Prefab supports context for intelligent rule-based evaluation of get and isFeatureEnabled based on the current request/device/user/etc.

Given

const context = new Map([
  [
    "user",
    new Map([
      ["key", "some-unique-identifier"],
      ["country", "US"],
    ]),
  ],

  [
    "subscription",
    new Map([
      ["key", "pro-sub"],
      ["plan", "pro"],
    ]),
  ],
]);

You can pass this in to each call

  • prefab.get('some.config.name', context, defaultValue)
  • prefab.isFeatureEnabled('some.feature.name', context, false)

Or you can set the context in a block (perhaps surrounding evaluation of a web request)

prefab.inContext(context, (pf) => {
  const optionalJustInTimeContext = { ... }

  console.log(pf.get("some.config.name", optionalJustInTimeContext, defaultValue))
  console.log(pf.isEnabled("some.config.name", optionalJustInTimeContext, false))
})

Note that you can also provide Context as an object instead of a Map, e.g.:

{
  user: {
    key: "some-unique-identifier",
    country: "US"
  },
  subscription: {
    key: "pro-sub",
    plan: "pro"
  }
}

Option Definitions

Besides apiKey, you can initialize new Prefab(...) with the following options

| Name | Description | Default | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | | collectEvaluationSummaries | Send counts of config/flag evaluation results back to Prefab to view in web app | true | | collectLoggerCounts | Send counts of logger usage back to Prefab to power log-levels configuration screen | true | | contextUploadMode | Upload either context "shapes" (the names and data types your app uses in prefab contexts) or periodically send full example contexts | "periodicExample" | | defaultLevel | Level to be used as the min-verbosity for a loggerPath if no value is configured in Prefab | "warn" | | enableSSE | Whether or not we should listen for live changes from Prefab | true | | enablePolling | Whether or not we should poll for changes from Prefab | false |