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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@rangler/connect-js

v0.1.9

Published

Hosted Rangler Connect JavaScript SDK for read-only account and portfolio linking.

Downloads

129

Readme

Rangler Connect JS

JavaScript SDK for Rangler Connect read-only account and portfolio linking.

Install

npm install @rangler/connect-js

Use with npm

Create a link token on your backend, then let the SDK fetch it when the user opens Connect.

Keep rgl_test_ and rgl_live_ API keys on your backend only. fetchLinkToken should call your own backend endpoint; that endpoint should create the short-lived rgl_link_ token with X-API-Key.

import { Connect } from '@rangler/connect-js';

const connect = new Connect({
  fetchLinkToken: async () => {
    const response = await fetch('/api/rangler/link-token', { method: 'POST' });
    const data = await response.json();
    return data.link_token;
  },
  environment: 'test',
  onSuccess: async ({ public_token }) => {
    await fetch('/api/connect/exchange', {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify({ public_token }),
    });
  },
  onClose: ({ status }) => {
    console.log(status);
  },
  onEvent: (eventName, payload) => {
    console.log(eventName, payload);
  },
});

connect.setup().open();

You can also pass a pre-created linkToken directly.

The public token is one-use and must be exchanged by your backend with X-API-Key.

Use with a script tag

Load the standalone browser build, then initialize Connect from window.RanglerConnect. Define window.RanglerConnect.onLoad before the async script loads; otherwise the SDK may load before your callback is registered.

<button id="connect">Connect portfolio</button>
<script>
  window.RanglerConnect = window.RanglerConnect || {};
  window.RanglerConnect.onLoad = function () {
    var connect = window.RanglerConnect.init({
      environment: 'test',
      fetchLinkToken: async function () {
        var response = await fetch('/api/rangler/link-token', { method: 'POST' });
        var data = await response.json();
        return data.link_token;
      },
      onSuccess: async function ({ public_token }) {
        await fetch('/api/rangler/exchange-token', {
          method: 'POST',
          headers: { 'Content-Type': 'application/json' },
          body: JSON.stringify({ public_token }),
        });
      },
    });

    document.getElementById('connect').onclick = function () {
      connect.open();
    };
  };
</script>
<script src="https://connect.rangler.co/connect.js" async></script>

API

new Connect(options)

  • linkToken: short-lived rgl_link_ token created by your backend.
  • fetchLinkToken: async function that returns a fresh rgl_link_ token. Use this when opening Connect from a button.
  • environment: test or live. sandbox is accepted as a deprecated alias for test.
  • widgetOrigin: optional override for development.
  • reference: optional customer-side reference string.
  • onLoad: called when Connect is ready.
  • onSuccess: called with { public_token, connection_id, institution_id }.
  • onClose: called when the user closes or cancels the flow.
  • onError: called for widget error exits.
  • onEvent: called for lifecycle events.

Methods:

  • setup(config?): prepares Connect without showing it.
  • open(): opens Connect.
  • close(): closes Connect.
  • destroy(): removes Connect and its listeners.