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

@subifinancial/subi-connect

v6.0.0

Published

Subi Connect is a React component library that can be used to easily add UI with Subi's core business logic.

Readme

Subi Connect is a React component library that can be used to easily add UI with Subi's core business logic.

🔗 Links

👨‍💻 Basic Integration

Basic integration instructions are provided below. Please visit our docs 📄 for a more in-depth setup guide.

Step 1 - Installation

npm install @subifinancial/subi-connect
npm install @tanstack/react-query @tanstack/react-table

Step 2 - SubiConnectProvider

Add the Subi Connect Provider to your application. This must come after your QueryClientProvider and encompass all Subi Connect components. We will discuss your connectionFn below.

import { SubiConnectProvider } from '@subifinancial/subi-connect';
import { QueryClient, QueryClientProvider } from '@tanstack/react-query';

const queryClient = new QueryClient();

function App() {
  /**
   * Your internal id reference to the company and their name.
   * For example:
   *  - You have company A who uses your services.
   *  - You will provide their id along with their name as viewed in your database.
   *  - The name is used for sanity checking; we will not use this.
   */
  const company = { referenceId: someCompanyId, name: 'Company A' };

  const connectionFn = useCallback(
    async () => await yourFnToGetSubiConnectAccessToken(company),
    [someCompanyId],
  );

  return (
    <QueryClientProvider client={queryClient}>
      <SubiConnectProvider
        connectionFn={connectionFn}
        companyContext={company.referenceId}
      >
        ...
      </SubiConnectProvider>
    </QueryClientProvider>
  );
}

Step 3 - connectionFn

The connection function needs to speak to your backend to get the API key. This helps with security by not exposing your Subi Connect API Key to the frontend.

The core idea is to hit our https://subiconnect-api.subi.au/subi-connect/authentication/company-access-token endpoint to generate a company access token with your Subi Connect Account API Key and company data. Each company using your service will have their own generated access token.

📫 Support

  • Feel free to email our support team
  • Open up an issue on Github

🕵️ Development / Storybook

  1. npm install
  2. npm run build-storybook
  3. npm run storybook
  • Ensure you select your TARGET_ENV with TARGET_ENV=local npm run ...
  • View the README docs in /demo for more information