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

api-communication

v1.0.3

Published

ES6 Class for API communication

Downloads

11

Readme

API Communication

Most web applications communicate with a server, but once the app is built often offline has not been considered. This class bridges a small part of the offline gap allowing requests that occur when the useris offline to be stored in the browser localstorage.

Usage

Get the package from npm

npm i api-communication

Setup

Easiest way to use is to include this class as you would include any other es module to your lit application.

import { ApiCommunication } from 'api-communication';

Create an instance of it set the properties then either set the id especially if you intend to have multiple. Keep it simple, one is often better than many.

Here you can setup the listeners to for the success and or failure events. You can set the names of these events as they are attributes on the class.

  constructor() {
    this.communication = {};
    this.communication = new ApiCommunication;
    this.communication.url = 'https://jsonplaceholder.typicode.com/todos/1';
    window.addEventListener('success', (response) => {
      this.handleSuccess(response);
    });
    window.addEventListener('failure', (response) => {
      this.handleFailure(response);
    });
  }

Set the properties you need for the current call

this.communication.cache = 'no-cache';
this.communication.method = 'GET';

Firing the request

Then fire the action

this.communication.fire();

Getting a response

There are currently two methods of getting a response, the first is the fire function returns a value asyncronously OR You can listen to the success or failure events. This is the suggested method as you can handle them based on your ID that you set.

  handleSuccess(response) {
    this.info = response.detail.response.title;
  }

  handleFailure(response) {
    this.info = response.detail.response.status;
  }

  render() {
    return html`
      <div class="theinfo">${this.info}</div>
    `
  }

Offline

The reason the best method is to listen to the success or failure events is that when returning online you won't have the luxury of a returned value on the fire method. However, the success or failure events are still triggered. This way your app can seamlessly update the data which in turn will update the users UI.

  render() {
  handleSuccess(response) {
    this.info = response.detail.response.title;
  }

  handleFailure(response) {
    this.info = response.detail.response.status;
  }

  return html`
      <div class="theinfo">${this.info}</div>
    `
  }

Profit

Hopefully this serves you well, remember any suggestions and bug fixes can be requested through merge requests or issues.