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

element-customer-portal-sdk

v0.9.0-rc.320

Published

SDK to build customer portals connecting to ELEMENT

Downloads

23

Readme

Blueprint UI components

For use with partner customer portals

Using it

This section is still work in progress.

Don't forget to register a handler that gets triggered whenever the ELEMENT backend identified that the current user is no longer authenticated (expired JWT token, invalid JWT token, ...). In the handler you should most probably redirect the user to the login screen.

import {authService} from "element-customer-portal-sdk";

authService.registerLoginRequiredHandler(() => {
    window.location.href = '/'
})

Conventions

Uses the same eslint configuration as the create-react app projects.

Building

Install dependencies

yarn install

Running the build in watch mode

yarn dev

Running tests:

yarn test

Use storybook to view the components you are building in isolation

yarn storybook

Developing components and using them directly in other projects without having to release them every time

In this repo run

yarn link

Then in the repo you want to use the current files run

yarn link element-customer-portal-sdk

Now the 2 projects are coupled together via filesystem symlinks, whenever you change something in this project make sure to have yarn dev running, so the files are automatically re-built and ready to be used in your consuming project.