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

waypost-sdk-react

v1.0.1

Published

Waypost's SDK for client-side web applications

Downloads

3

Readme

Waypost Client-Side SDK for JavaScript

Official Usage Docs

This is Waypost's SDK for React web applications.

  1. Install via npm install waypost-sdk-react (https://www.npmjs.com/package/waypost-sdk-react)
  2. Import the package at the top of your React application's App.js file. Inside the Config constructor, the first argument is your SDK Key that you can get from the Waypost feature flag manager UI. The second argument is the address of the Waypost flag provider service. See the example code below:
import * as waypost from 'waypost-sdk-react';

const { Config, WaypostProvider } = waypost;
const config = new Config('1a2b3c4d5e', "http://localhost:5050");
  1. Wrap your App component inside the WaypostProvider context provider. Example:
function App() {
  return (
    <WaypostProvider config={config}>
      ...
    </WaypostProvider>
  );
}
  1. Now you can access the sdkClient from other parts of the app by using:
const { sdkClient } = useContext(WaypostContext)
  1. To add the user_id or any other identifier to the SDK, which will assign the treatment (whether they will receive the feature), use the addContext() method on the sdkClient, and pass in an object containing the key userId and the value. Example:
sdkClient.addContext({ userId: newUserId });
  1. Wherever you need to branch your code based on the feature flag status, call the evaluateFlag() method on the sdkClient object. The evaluateFlag() method takes the name of the feature flag as the required argument, and optionally a default value if the feature flag data is unavailable. The function returns a boolean denoting whether the status is on or off (if a userId is provided, it is decided based on a hashing algorithm). Example:
const useNewHeader = sdkClient.evaluateFlag('Turquoise Header', false);
if (useNewHeader) {
  return <NewHeader />
} else {
  return <Header />
}