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

vue-render-scan

v0.1.0

Published

Visualize Vue component rerenders in development.

Readme

Vue Render Scan

Visualize Vue component redraws while you develop. This is an early Vue/Nuxt equivalent of React Scan: it watches Vue component mount/update cycles and flashes the DOM bounds of components that redrew.

Install

pnpm add -D vue-render-scan

Vue

import { createApp } from 'vue'
import { VueScanPlugin } from 'vue-render-scan'
import App from './App.vue'

createApp(App)
  .use(VueScanPlugin, {
    enabled: import.meta.env.DEV,
    includeMounts: false
  })
  .mount('#app')

Nuxt

export default defineNuxtConfig({
  modules: ['vue-render-scan/nuxt'],
  vueScan: {
    enabled: process.env.NODE_ENV !== 'production',
    includeMounts: false,
    threshold: 0
  }
})

API

import { getReport, scan, setOptions } from 'vue-render-scan'

const handle = scan(app, {
  enabled: true,
  includeMounts: false,
  threshold: 1,
  ignore: [/RouterLink/],
  onRender(event) {
    console.log(event.componentName, event.type, event.duration)
  }
})

setOptions({ enabled: false })
getReport()
handle.getStats()
handle.stop()

Development

npm test
npm run typecheck
npm run build

The test suite mounts real Vue apps in jsdom and verifies that component updates emit redraw events, respect filters, and update reports.

Options

| Option | Default | Description | | --- | --- | --- | | enabled | true in development | Turns scanning on or off. | | includeMounts | false | Also show first mounts, not only updates. | | log | false | Logs render events to the console. | | showToolbar | true | Shows the floating status toolbar. | | showOverlay | true | Flashes component bounds after redraws. | | threshold | 0 | Minimum measured lifecycle duration in ms. | | maxEvents | 250 | Reserved for event history consumers. | | ignore | [] | Component name filters to suppress. | | only | [] | Component name filters to exclusively track. | | onRender | undefined | Callback for every tracked event. |

Notes

This package uses Vue lifecycle hooks through a global mixin. It reports component updates that Vue exposes through beforeUpdate and updated, then measures the elapsed wall-clock time around that component lifecycle pair. That is useful for finding noisy redraws, but it is not a replacement for Vue Devtools flamegraphs or browser performance traces.

Install this before the root component mounts. It is dev-only by default and should stay disabled in production unless you explicitly need field diagnostics.