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

@wisersolutions/launchdarkly-node

v0.0.1

Published

LaunchDarkly SDK (Node.js, server-side) wrapper intended to provide a modern API and enforce best practices.

Downloads

2

Readme

launchdarkly-node

LaunchDarkly server-side SDK wrapper for Node intended to provide a modern API and enforce best practices.

Use

Init connection to LaunchDarkly when launching your app with

const { init } = require('@wisersolutions/launchdarkly-node')

async function startApp() {
  await init('YOUR_LAUNCH_DARKLY_APP_KEY', options)
  // … launch the rest of your app
}

Then request a feature variation anywhere in your app with

const { variation } = require('@wisersolutions/launchdarkly-node')

async function handleSomeRequest(context) {
  const user = getUserFrom(context)
  const isFeature1Enabled = await variation('some-boolean-flag-key', user)
  const feature2Variation = await variation('some-multi-variant-flag-key', user, 'default-variant')
  
  if (!isFeature1Enabled) return /* … */

  switch (feature2Variation) {
    case 'variant-one': return /* … */
    case 'variant-two': return /* … */
    case 'default-variant':
    default: return /* … */
  }
}

See SDK docs for argument details.

Development

Install

Install dependencies using:

npm install

Develop

After you modify sources, run the following (or set up your IDE to do it for you):

  • format the code using npm run format
  • lint it using npm run lint
  • test it using npm test

and fix the errors, if there are any.

Publish

Publishing is done in two steps:

  1. Create a new version tag and push it to the repository:
    npm version <patch|minor|major>
    git push --follow-tags
  2. Build and publish the new version as a npm package:
    npm publish --access public