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

ts-api-toolkit

v2.0.16

Published

A simple wrapper around Redaxios in combination with JWT/Auth Token Handling to easily communicate with an API, with or without authorization

Downloads

10

Readme

TS-API-Toolkit is a simple way to handle your API calls as well as your localStorage JWT management. The library offers a simple wrapper around redaxios in conjunction with a service to handle your JWTs. No longer will you need to attach tokens to every request or even manually worry about them. Just set the token, and it'll be attached to every call you make.

Install

$ yarn add ts-api-toolkit

Usage

import { apiService, authStorageService } from 'ts-api-toolkit';

const { data: { user } } = await apiService.post('users/login', credentials);
authStorageService.saveToken(user.token);

API

This library offers two class instance exports, ApiSerivce and AuthStorageService. Using these you can easily handle your application.

import { authStorageService } from 'ts-api-toolkit'

Provides an instance of AuthStorageService.

  • .changeTokenKey(tokenKey: string): void

    Changes the key your token is stored under in localStorage.

    The token key is what identifies your token as it is saved in a browser's localStorage. The value from that key is attached to every API request.

  • .getToken(): string

    Retrieves the current value for your token key. If a value cannot be found, returns an empty string.

  • .saveToken(token: string): void

    Saves a provided token into localStorage using the tokenKey.

    The token you save will be used with all future API requests, until it is removed or changed.

  • .destroyToken(): void

    Removes the currently stored token key and value.

import { apiService } from 'ts-api-toolkit'

Provides an instance of ApiService.

  • .changeBaseUrl(baseUrl: string): void

    Changes the base URL to use when making requests.

    Use the baseUrl parameter to describe your base API URL. Use a partial route like /api if you want to use a proxy, otherwise, set the full route to your API like http://example.com/api. The default baseUrl is /api/v1.

  • .changeAuthSchema(authSchema: string): void

    Changes the scheme used in the Authorization header.

    Use the authSchema parameter to describe the prefix to the token. The default is set to Bearer, so, unedited, all API requests will come with the following header: Authorization: 'Bearer <auth-token>'

  • .get(resource: string, params?: Record<string, unknown>): Promise

    GET request

  • .post(resource: string, data: Record<string, unknown>, params?: Record<string, unknown>): Promise

    POST request

  • .put(resource: string, data: Record<string, unknown>, params?: Record<string, unknown>): Promise

    PUT request

  • .patch(resource: string, data: Record<string, unknown>, params?: Record<string, unknown>): Promise

    PATCH request

  • .delete(resource: string, params: Record<string, unknown>, params?: Record<string, unknown>): Promise

    DELETE request

  • .options(resource: string, params?: Record<string, unknown>): Promise

    OPTIONS request

All requests use the Authorization header to send the current token in localStorage, regardless of whether it is empty.

Query parameters will all be properly serialized, no need to provide anything beyond an object.

`{ name: 'ferret', color: 'purple' }` -> `?name=ferret&color=purple`

License

MIT © Ryan Christian