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

next-feature-flags-client

v8.7.8

Published

[Feature toggles](http://martinfowler.com/bliki/FeatureToggle.html) for Next with ability to override using `x-flags` header or `next-flags` cookie. Also sends reports to sentry of any expired flags still in use.

Downloads

107

Readme

Next feature flags client Circle CI

Feature toggles for Next with ability to override using x-flags header or next-flags cookie. Also sends reports to sentry of any expired flags still in use.

📣 DEPRECATION NOTICE

This package has been moved in npm to be part of the @financial-times org, and so it has a new home (and slightly different package name): @financial-times/n-flags-client.

The version you’re viewing now will no longer be maintained. Please check https://github.com/Financial-Times/n-flags-client/releases for the latest release notes and update your app’s package.json.

Usage

Client side

Client side feature flags are no handled in n-ui and are passed in to the bootstrap() method

Server side

Does not need to be constructed with an object of values. This is taken care of by next-express, as is middleware for making flags available to requests. By default will request from next's set of platinum flag services, but can be overridden using the setUrls([arr]) method.

The default behaviour when NODE_ENV=production is to get overrides from the http header that Fastly sets. For apps that not routed via Fastly you can set OVERRIDE_FLAGS_FROM_COOKIE=true to get overrides from a cookie.

API

init(options)

Initialises the flag client. Options may have 3 self-explanatory properties:

  • timeout - length of time to wait for response from the flag server [default 3000]
  • interval - interval between attempts to fetch fresh flag data [default 30000]

Returns a promise that is resolved when flags have been successfully fetched at least once (or that resolves immediately if none of the above options are passed)

getArray()

Returns a simplified array of flags similar to that retrieved from the flags api, but lacking expiry date information.

get(name)

Returns the current state of a flag (or false if the flag doesn't exist). If no name is provided it returns a hash of all current flag objects, including information on expiry dates

getModel(name)

Returns a flag model for the named flag. If {withAb: true} is passed in in the options to any of this module's components, it will eventually propagate down to make ab test information is available on the ab property of each flag's model