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

@yrobot/sw-proxy

v1.0.0

Published

a client proxy for all url requests in the website, based on service worker.

Downloads

6

Readme

Demo

Design

Thanks to the Service Worker, we can intercept all requests in the website, and then we can return the response we want.

But, as for the secure reason, we can't register the Service Worker from a inline data url, so you have to serve the Service Worker by yourself, But i can handle the logic inside the Service Worker.

So i will split the repo into two parts, one is the client part, which handle the logic inside html, and the other is the sw part, which handle the logic inside the Service Worker.

Usage

1. Install @yrobot/sw-proxy

yarn add @yrobot/sw-proxy

2. Import @yrobot/sw-proxy/sw

service-worker.ts

import "@yrobot/sw-proxy/sw";

3. Import @yrobot/sw-proxy/client and use it

import SWProxy from "@yrobot/sw-proxy/client";

(async () => {
  // init the swProxy
  await swProxy.register();

  // set the proxy list
  await swProxy.set([
    {
      url: "/get",
      response: {
        body: "hello world",
      },
    },
    {
      url: "/post",
      method: "POST",
      response: async () => ({
        body: JSON.stringify({
          time: new Date().toLocaleString(),
          name: "sw-proxy",
        }),
        options: {
          headers: {
            "content-type": "application/json",
          },
        },
      }),
    },
    {
      url: "/image.png",
      response: {
        body: new Blob(), // image blob
      },
    },
  ] as ProxyItem[]);

  // add proxy item
  await swProxy.add([
    {
      url: "/image2.png",
      response: {
        body: new Blob(), // image blob
      },
    },
  ] as ProxyItem[]);

  // remove proxy item
  await swProxy.remove(["/image.png"] as ProxyURL[]);

  // get current active proxy list
  swProxy.list();

  // clear all proxy
  await swProxy.clear();

  // unregister the seProxy
  await swProxy.unregister();
})();

Structure

Common

type ProxyURL = string; // support RegExp later maybe

ProxyItem

interface FetchHandlerParams {
  pathname: string;
  url: string;
  search: Record<string, string>;
}

interface ResponseConstructor {
  body:
    | string
    | null
    | Blob
    | ArrayBuffer
    | DataView
    | FormData
    | ReadableStream
    | URLSearchParams;
  options?: ResponseInit;
}

interface ProxyItem {
  url: ProxyURL;
  method?: string;
  response:
    | ResponseConstructor
    | ((params: FetchHandlerParams) => Promise<ResponseConstructor>);
}