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 🙏

© 2026 – Pkg Stats / Ryan Hefner

pa-egloff

v0.2.9

Published

tracker for bachelor thesis

Readme

PA.EmotionsTracker

The EmotionalAwareness-Tool consists of two parts: a tracker, where webcam images are processed and the estimates regarding valence, fatigue and engagement are calculated, and a client that visualizes the estimates.

This is the tracker project, the client can be found here

This project is published on npm

Documentation

Used tensorflow models

Endpoints

Communication with the tracker is done over IPC. The following endpoints exist:

Incoming

  • start-tracker to start the tracker
  • pause-tracker to pause the tracker
  • set-low-performance-mode with payload: boolean to activate/deactivate low performance mode

Outgoing

  • face-api-expression with payload: FaceApiExpression
  • face-api-head-orientation with payload: FaceApiHeadOrientation
  • face-api-aggregated-expression with payload: FaceApiAggregatedExpression
  • face-api-smiled-once with payload: FaceApiHasSmiled
  • face-api-raw-expressionswith payload: string

  • facial-landmarks-data with payload: FacialLandmarksData
  • facial-landmarks-blink-count with payload: FacialLandmarksBlinkCount

  • pose with payload: PoseData

  • z-deviation with payload: ZDeviation
  • head-orientation-deviation with payload: HeadOrientationDeviation
  • metric-log with payload: MetricLog
  • estimated-dimensions with payload: EstimatedDimensions
  • update-tracker-status with payload: Status to get the current state of the tracker

Main Components

The following diagram shows the main dataflow of the program. For the sake of clarity, the Renderer is not depicted. The Renderer handles incoming requests from the client, like starting/pausing or switching to low performance mode.

Open issues concerning coupling between tracker & client

  • Tracker: pa-shared interface is no longer used

  • Client: in package.json, we need to know exact folder structure of tracker

    "html": "./node_modules/emotions-tracker/src/renderer/index.html",
    "js": "./node_modules/emotions-tracker/src/renderer/renderer.ts",
    "name": "tracker_window"
  • Client: in webpack.plugins.js, we have to copy the whole assets folder from the tracker to the client, because the tracker_window needs access to models / images

    {
      from: path.resolve(__dirname, "node_modules/emotions-tracker/src/renderer/assets"),
      to: path.resolve(__dirname, ".webpack/renderer/assets"),
    }