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

network-information-api

v0.0.1

Published

Network information api polyfill

Downloads

8

Readme

Network Information Api polyfill

An attempt to create polyfill for this specification. Polyfill is based on pinging some url and latency analysis. These are pretty rough measurements. But better than nothing.

Usage

npm i -S network-information-api-polyfill

or just

<script src="dist/main.js"></script>

Then you need to initialize it

new NetworkInformationApiPolyfill().then(connection => {
    console.log(connection); // or navigator.connection

    connection.addEventListener('change', e => {
        console.log('change', e);
    });
});

Polyfill must do the first request, to get information about network. So you can't use it synchronously, only using promise.

Configuring

You can pass options during initialization:

new NetworkInformationApiPolyfill({
    // here
});
pingMaxTimeout

Type: number
Default: 5000

Timeout of request. After this time, the network will be considered unavailable (navigator.connection.type === 'none).

pingFrequency

Type: number
Default: 6000

A frequency of pinging.

pingUrl

Type: string Default: ${location.protocol}//network-information-api.surge.sh/1b.txt

An url, that will be pinged. It is strongly recommended to have your own address. It improves the accuracy of measurements in relation to the user of your service.

CSP rules

If you have CSP rules, and you don't want own pingUrl, you must add url network-information-api.surge.sh to rule connect-src.