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

ic-api-caller

v2.0.0

Published

Caller used to call internal and external APIs passing auth and refresh tokens on headers for authenticated endpoints

Downloads

37

Readme

IC-API-CALLER

its a simple library that focus on make API calls simpler. By this concept the instanced object will have some information passed down its constructor, which will be used to ensure that all calls from this instances will be done in the same domain, tha path however is informed in the method called.

For the implementation we have two kinds of methods parameters:

// POST, PUT parameters
{
    path: string;
    body: unknown;
}

// GET, DELETE parameters
{
    path: string;
}

The path will be concatenated with the base url informed in the object creation to form the called url and the body will be foward on the call;

The constructor object should follow this interface:

{
    base_url: string;
    auth_token?: string;
    refresh_tokens?: {
        path: string;
        body: unknown;
        token: string;
        base_url: string;
    }
}

The base_url defines the domain in which the instanced object will request informations, auth_token will be added in the requests header to ensure that authetication is done properly (we only suport token bearer authentication at the moment), refresh_tokens is composed by information needed to refresh the auth token if it expires. The path and base_url in the refresh_tokens enseure that we can refresh tokens when needed even if the path or base url are different than the actual requests urls and paths, the token property ensures that we can foward the refresh token to the called endpoints and the body ensures that the refresh token request sends the correct body when requesting token refresh.

The implementation should occour like the following:

import Api from 'api-caller';

const api = new Api(connection_info);
const result = api.get(get_parameters);