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

@complyco/client-documents-web

v5.2.0

Published

ComplyCo's client web document widget

Downloads

8

Readme

Client-Web

This package allows you to display documents and tasks and collect consents in your web apps.

Getting Started

Please note, the baseUrl comes from the client that you have registered in ComplyCO's dashboard. It will look like app-<...>.client.complyco.com.

The onAuthTokenRequested callback will need to hit an endpoint on your backend which is configured to generate and sign a JWT. The client that you have registered in ComplyCO's dashboard should be configured with the public key that corresponds with the private key used for signing in your backend API.

import { Overview } from "@complyco/client-documents-web/views";

const view = Overview.initialize({
  baseUrl,
  iframe: document.getElementById("myIframe"), // this is optional
  onAuthTokenRequested,
  onLoad,
  onStarted,
  onShutdown,
  onResize,
  onComplete,
  onHeartbeatAge,
});

Lifecycle

Note, if iframe isn't passed, then you can call view.run(iframe) in the future. This can be useful if you want to wait for onStarted to fire prior to opening a Dialog (where the iframe isn't mounted in the DOM until the Dialog is open).

You can call view.unmount() to clean up the event listeners that are managing the iframe.

Event callbacks

  • onStarted: This is called when the view starts, but before it loads. This is useful for cases such as the Tasks.List view where onStarted will only run if there are tasks for the user to see. This can help you avoid loading a dialog unnecessarily.
  • onLoad: This is triggered by the iframe's onload event.
  • onShutdown: This is run if the contents of the iframe shutdown, such as in the case of an unrecoverable error.
  • onResize: The screens in the iframe will send their preferred size ("small" or "large") so that your UI can resize if you so choose.
  • onComplete: This is run when a consent achieves a completed state.
  • onHeartbeatAge: This returns the age of the last ping that the View does to the iframe. You can use this to automatically close the iframe if it becomes non-responsive.

Views

  • Tasks.List: Renders a list of pending tasks for the user.
  • Tasks.Details: Renders a task by ID for the user.
  • Overview: Renders a section of pending tasks (if any) and historical consents (if any) for the user.
  • Consents.Details: Renders a consent by ID for the user.