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

flux-sdk-node

v0.5.2

Published

Flux JavaScript SDK for Node clients

Downloads

22

Readme

Flux Node SDK

Installation

  1. Install Node >= 4 Earlier versions may work, but should be used with caution.
  2. npm install --save flux-sdk-node
  3. Have fun!

Environment Configuration

NODE_ENV: By default, the SDK runs in debug/development mode. Set NODE_ENV to production to exit development mode.

Development

flux-sdk-node provides a thin wrapper around flux-sdk-common in order to set up a node-specific environment (e.g., it sets up web sockets). Most development happens in flux-sdk-common.

Testing

flux-sdk-node contains end-to-end tests. The core test suite is located in flux-sdk-node/spec.

NOTE: Unfortunately, the end-to-end test suite is currently very stateful. This affects both writing and running tests.

This test suite requires the following environment configuration:

CLIENT_ID: Your (test) client ID

CLIENT_SECRET: Your (test) client secret

FLUX_URL: The URL of the Flux genie server you are testing against.

TEST_EMAIL: Your test account's email address

TEST_PASSWORD: Your test account's password

DEBUG (default: false): Set to true to make Nightmare visible

EXAMPLE_PORT (default: 4567): Set to change the port used in any tests that set up a full server (i.e., the auth flow tests).

SKIP_AUTH_FLOW (default: false): Set to bypass the auth flow when running tests. This requires ACCESS_TOKEN and FLUX_TOKEN to be set.

ACCESS_TOKEN: Set if using SKIP_AUTH_FLOW is true. Must be a valid token, e.g., from an existing session.

FLUX_TOKEN: Set if using SKIP_AUTH_FLOW is true. Must be a valid token that corresponds to the provided ACCESS_TOKEN.

Environment

Step by step instructions for Flux employees on how to set up the environment are here: https://docs.google.com/document/d/1joaFumoetcAfN9xCU-ND7vr2dMUXPGaNqa6syz_EqyU/edit#