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

@algea_care/xpertyme-api

v1.4.4

Published

Just a little lib for the xpertyme api

Downloads

179

Readme

What❓

This is a little package for talking to the expertyme api in typescript

Why 🤷‍♂️

The point of this lib is to allow consumers to

  • have typings for various xpertyme apis
  • just consume functions like 'getUsers' and not worry about generating tokens etc
  • abstract away all type casting / error handling and all other api related chores

It just makes it easier to talk to the apis from one central code base

How ⚙️

Just npm i you are good to go (if working on this package)

if consuming

npm i @algea_care/xpertyme-api and use it in your project like so


import const { user } from '@algea_care/xpertyme-api'

const myNewUser = await user.create({email: '[email protected]', ...})

The result of the call and the payload to it will already by typecast etc for you

Structure

There are not just one but a few places to get data from (apis) so what is exported is an object where each key represents an api that you can talk to.

there is one place that we request access tokens as the tokens work on all apis. That means you need to provide some env vars when using the package (to get the access tokens), see config

Configuration 🔧

Have a look at env.example but essentially you need to state the api domain, client secret and client id and you are good to go 🚀