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

@dashkite/breeze-client

v1.1.0-beta.0

Published

Web Component and OAuth handler for use with the Breeze authentication API

Downloads

4

Readme

Breeze Client

Web Component for use with the Breeze authentication API.

Install

npm i @dashkite/breeze-client

Usage

In your application, import Breeze Client:

import "@dashkite/breeze-client"

In your markup for your login page, create an instance of the component:

breeze-connect(
  data-display-name = "Acme, Inc."
  data-domain = "acme.com"
)

If the client has not yet authenticated, this will display a list of buttons for each supported provider.

If the client is already authenticated—meaning there is already a profile stored locally—the component will display a success message and generate a success event.

If the client state is undefined, the component will attempt to restore a well-defined state, possibly starting with the list of providers.

Warning: The component may lose authentication state attempting to restore a well-defined state locally. Your application should attempt to establish a well-defined state prior to loadiing the component.

You may determine the state of local client using the Zinc library. It's the responsibility of your application to try to define an application profile, if applicable. For example, if your application allows for multiple profiles, you should ensure that you determine which profile to use prior to loading the component.

You may determine whether a device is authenticated using the isAuthenticated function exported by Breeze Connect.

import { isAuthenticated } from "@dashkite/breeze-connect"

do ->

  if (await isAuthenticated())
    console.log "Authenticated!"
  else
    console.log "Not yet authenticated."