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

@wizeworks/lens-vue

v0.3.0-alpha.11

Published

WizeLens for Vue 3 apps: a plugin that links browser calls to server traces, sends page views from vue-router, and reports component errors.

Readme

@wizeworks/lens-vue

WizeLens for Vue 3 apps: a plugin on top of @wizeworks/lens-browser that links every fetch and XMLHttpRequest to its server trace, sends page views from vue-router, and reports the errors Vue catches with the component that threw them.

Install

npm install @wizeworks/lens-vue
// main.ts
import { createApp } from "vue";
import { WizeLens } from "@wizeworks/lens-vue";
import App from "./App.vue";
import { router } from "./router";

createApp(App)
  .use(router)
  .use(WizeLens, { endpoint: "/_wizelens", router, enabled: import.meta.env.DEV })
  .mount("#app");

Vue 3 and vue-router 4. The package does not import vue, so it adds nothing to your bundle beyond WizeLens itself.

What it does

  • Starts WizeLens on the page: every fetch and XMLHttpRequest gets a traceparent header, and page views, Web Vitals, browser errors, and console lines are sent.
  • Sets app.config.errorHandler, and keeps the handler your app already had (it still runs). Each error carries vue.component, vue.component.trail ("App > Cart > PriceLine"), and Vue's vue.info.
  • With router, each finished navigation is a page view. Failed or cancelled navigations are not.
  • Shows the in-page HUD (see below).

Options

All @wizeworks/lens-browser options, plus:

| Option | Description | |---|---| | router | Your vue-router instance. | | lens | An instance from initWizeLens to use instead of starting one. | | hud | The in-page HUD: true, false, or "auto" (default). | | slowMs | The HUD shows requests at or over this many ms as "warning". Default 500. |

The HUD

The same HUD as every WizeLens browser package: the last request, its server trace, errors, and links into the dashboard, in a <wizelens-hud> element with its own shadow root, so your CSS cannot reach it.

  • "auto" (default) asks {endpoint}/api/info once and shows the HUD when the server's read API answers, as in development. A send-only server shows nothing.
  • true shows it and reads traces back from the server.
  • false shows nothing and reads nothing back.
app.use(WizeLens, { endpoint: "/_wizelens", router, hud: true, slowMs: 800 });

When a .NET or Node add-on puts its HUD script into the pages it serves in development, the plugin takes over from it: one HUD and one capture per page.

In components

import { inject } from "vue";
import { WIZELENS_KEY, type WizeLensInstance } from "@wizeworks/lens-vue";

const lens = inject(WIZELENS_KEY) as WizeLensInstance;
lens.setUser(user.id);

this.$wizelens works in the Options API.

MIT licensed.