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

@wcgw/vibe-check-core

v0.1.3

Published

Framework-agnostic performance monitoring engine with AI/vibe-coding issue detection

Readme

@wcgw/vibe-check-core

Framework-agnostic browser performance monitoring engine with AI/vibe-coding issue detection. Zero runtime dependencies.

Installation

npm install @wcgw/vibe-check-core

Usage

import { VibeCheckEngine } from '@wcgw/vibe-check-core'

const engine = new VibeCheckEngine()
engine.start()

// Get a performance snapshot
const snapshot = engine.getSnapshot()
console.log(snapshot.frameRate.fps)
console.log(snapshot.issues)

// Subscribe to snapshot updates
const unsubscribe = engine.onSnapshot((snapshot) => {
  if (snapshot.issues.length > 0) {
    console.warn('Performance issues detected:', snapshot.issues)
  }
})

// Clean up
engine.stop()
unsubscribe()

Configuration

const engine = new VibeCheckEngine({
  // Send snapshots to an MCP server
  beaconUrl: 'http://localhost:4200',
})

Collectors

Collectors measure browser metrics continuously:

  • Frame Rate -- FPS, frame times, dropped frames via requestAnimationFrame
  • Long Frames -- Long Animation Frames (LoAF) API with script attribution
  • Web Vitals -- LCP, CLS, INP via PerformanceObserver
  • Memory -- JS heap size via performance.memory
  • Resources -- Resource loading performance and sizes
  • Console -- Tracks console.log/warn/error volume

Detectors

Detectors analyze snapshots and flag issues. All eleven are enabled by default; toggle them via config.detectors.

| Detector | What it catches | |----------|----------------| | dom-bloat | Excessive DOM nodes, deep nesting | | duplicate-requests | Repeated fetches to the same URL within 2s | | console-spam | High-volume console output | | memory-leak | Steadily growing heap usage | | layout-thrashing | Clusters of layout shifts without user input | | unoptimized-images | Images without width/height, missing lazy loading | | large-images | Oversized images for web delivery | | long-task-attribution | Long animation frames + script attribution (LoAF API) | | resource-bloat | Too many or oversized JS/CSS/image/font resources | | web-essentials | Missing viewport meta, lang attribute, etc. | | heavy-library | Detects 17 known heavy libraries (Three.js, MUI, Moment.js, Lottie, …) and warns about their performance pitfalls |

API

VibeCheckEngine

  • start() — begin monitoring
  • stop() — stop monitoring and clean up
  • isRunning(): boolean — whether the engine is currently running
  • getSnapshot(): VibeSnapshot — current performance snapshot
  • getIssues(): readonly VibeIssue[] — current issues from all enabled detectors
  • clearIssues(): void — clear the issues buffer on every detector
  • onSnapshot(cb): () => void — subscribe to snapshot updates (fires every 500ms). Returns an unsubscribe function.

Types

All types are exported: VibeSnapshot, VibeIssue, FrameRateStats, LongFrameStats, WebVitalsStats, HeapMemory, ResourceStats, ConsoleStats, VibeCheckConfig, Collector, Detector, DetectorName, Severity, etc. See src/types.ts for the full surface.

License

MIT