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

visit-stat

v3.0.1

Published

Website visitor statistics

Downloads

20

Readme

Visit-Stat

  • Lightweight
  • Statistics site_pv, site_uv, page_pv, page_uv
  • Storages Deta, MongoDB, Redis
  • Support ServerLess

Free Storage

Free Deploy

Usage

The following example uses the install dependency approach to deployment. You can just clone the repository and run node start.js.

mkdir visit-stat
cd visit-stat
npm install visit-stat

Create a new index.js

// index.js
require('visit-stat').server()

// If is ServerLess
// module.exports = require('visit-stat').main

After successful deployment, you can send requests through the front-end browser to perform access statistics

support GET and POST requests

// The unique identification of the statistics is determined by the referer in the request header.
// If the referer is `https://example.com` then `{ "site_pv": 2, "site_uv": 1 }`will be returned
// If referer is `https://example.com/post/xxxx.html` then `{ "page_pv": 2, "page_uv": 1 }`
// Visits to the root of the site will return site statistics, and visits to sub-pages of the site will return page statistics

// referer: https://example.com
// You need to set referrerPolicy to get the web page referer correctly, if you don't set referrerPolicy, the referer you get will probably be the root of the website every time.
fetch('http://localhost:6870', { referrerPolicy: 'no-referrer-when-downgrade' })
  .then((r) => r.json())
  .then(console.log)
// => { "site_pv": 23, "site_uv": 1 }

// referer: https://example.com/post/xxxx.html
fetch('http://localhost:6870', { referrerPolicy: 'no-referrer-when-downgrade' })
  .then((r) => r.json())
  .then(console.log)
// => { "page_pv": 3, "page_uv": 1 }

// Bulk access to statistical information (Maximum 20 URLs, and the `domain` of these 20 URLs must be the same as the referer, otherwise they will be filtered)
fetch('http://localhost:4200/visits', {
  method: 'post',
  body: JSON.stringify({ urls: ['https://example.com', 'https://example.com/post/xxxx.html'] })
})
  .then((r) => r.json())
  .then(console.log)
// =>
//[
//  {
//    "url": "https://example.com",
//    "site_pv": 23,
//    "site_uv": 1
//  },
//  {
//    "url": "https://example.com/post/xxxx.html",
//    "page_pv": 3,
//    "page_uv": 1
//  }
// ]