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

site-collector

v1.1.0

Published

<p align="center"> <img src="./resources/logo.png" width="512"/> </p>

Downloads

3

Readme

site-collector

site-collector is a convenient tool for collecting all kinds of data of websites.

Simple Example

import { createCollector } from "site-collector"

// pass config object
const collector = createCollector({

  // request properties
  url: ""
  headers: {},

  // global properties
  global: {  

    // static property
    signalType: "4G",

    // dynamic property
    // fn will be recalled when collect
    custom: () => store.custom
  }
})

// collect data
collector.collect({ myProperty: 'value' })

Multi Collector

import { createCollector } from "site-collector";

const collectorA = createCollector({
  url: "/a",
});
const collectorB = createCollector({
  url: "/b",
});

collectorA.collect({ name: "zxfan" });
collectorB.collect({ name: "king" });

Two request will be sent.

Advance

Override Config

collector.useConfig({
  url: ""
  headers: {},
  global: {},
})

Deprecate Report

set collector config

const collector = createCollector({

  // request properties
  url: ""
  headers: {},
  global: {}, // global properties
  deprecateRate: 1 // 0-1
})

deprecateRate:

  • if set 1, collector will deprecate all reports.
  • if set 0.5, collector will deprecate half reports.

Auto Collect

set these key to true. collector will collect these data automatically.

// all default false
collector.useAuto({
  scriptError: true,
  resourcesError: true,
  unhandledrejection: true,
  xhrAndFetchError: true,
  first: true,

  // web-vitals
  fcp: true,
  lcp: true,
  cls: true,
  network: true,
  fid: true
})

Options description:

  • scriptError: script error will be caught by window.onerror
  • resourcesError: Error that failed to load resource
  • unhandlerejection: uncatched Promise error
  • xhrAndFetchError: status of xmlHttpRequest and fetch is not 200
  • first: Time about page loading calculated by MutationObserver
  • fcp: First Contentful Paint
  • lcp: Largest Contentful Paint
  • cls: Cumlative Layout Shift
  • fid: First Input Delay
  • network: network data fetched by performance api(include ttfb)

Looking for more information about fcp lcp, Please read doc web-vitals

Transform properties

collector.useTransformer((task) => {
  return task;
});