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

@private-captcha/private-captcha-vue

v0.0.1

Published

Vue component for the client-side Private Captcha widget

Readme

Private Captcha Vue Component

A typed Vue 3 component for Private Captcha's client-side proof-of-work widget.

Installation

npm install @private-captcha/private-captcha-vue

Usage

The component must be rendered inside a form.

<script setup lang="ts">
import { ref } from 'vue';
import {
  PrivateCaptcha,
  type PrivateCaptchaEventDetail,
  type PrivateCaptchaExposed,
} from '@private-captcha/private-captcha-vue';

const captcha = ref<PrivateCaptchaExposed | null>(null);

function handleFinish(detail: PrivateCaptchaEventDetail): void {
  console.log('Captcha solved', detail.widget.solution());
}
</script>

<template>
  <form>
    <PrivateCaptcha
      ref="captcha"
      site-key="your-site-key"
      @finish="handleFinish"
    />
    <button type="button" @click="captcha?.reset()">Reset</button>
  </form>
</template>

The hidden solution field is added to the parent form by the widget and must be verified on your server.

Props

| Prop | Type | Default | |---|---|---| | siteKey | string | Required | | startMode | 'auto' \| 'click' | 'auto' | | debug | boolean | false | | fieldName | string | 'private-captcha-solution' | | puzzleEndpoint | string | Private Captcha endpoint | | displayMode | 'widget' \| 'popup' \| 'hidden' | 'widget' | | lang | Supported language code or 'auto' | 'auto' | | theme | 'light' \| 'dark' | 'light' | | styles | string | Widget defaults | | storeVariable | string | None | | eu | boolean | false | | compat | 'recaptcha' | None |

See the widget options documentation for option details.

All props except storeVariable are reactive and reset the widget with the current configuration. To change storeVariable, remount the component with a new Vue key.

Events

The component emits init, start, finish, error, and reset. Each event receives a PrivateCaptchaEventDetail containing the host element and the public widget facade.

Public Methods

A component template ref exposes:

  • execute(): void
  • reset(): void
  • solution(): string | null
  • element(): HTMLElement

Completion is reported through the finish event; execute() is intentionally not awaitable.

SSR and Cleanup

The package can be imported and server-rendered without browser globals. The core widget is created only after client mount.

The upstream core currently has no complete destroy API. This component removes its own listeners and resets the widget before unmount, but the core may retain its form focus listener when only the component is removed. Prefer keeping one widget mounted or unmounting its containing form at the same time.

Requirements

  • Vue 3.3 or later

License

MIT