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

@pollyou/vue

v0.1.0

Published

Vue 3 component, plugin and composable for PollYou surveys (wraps the <pollyou-survey> web component).

Readme

@pollyou/vue

Vue 3 component, plugin and composable for PollYou polls and surveys. Wraps the <pollyou-survey> web component of @pollyou/embed-core. Vue ≥ 3.4, SSR-safe (Nuxt), no compilerOptions.isCustomElement needed.

npm install @pollyou/vue
<script setup lang="ts">
import { PollYouSurvey } from '@pollyou/vue'
</script>

<template>
  <PollYouSurvey
    survey-id="AbC123xyz0"
    api-base="https://app.pollyou.app"
    :hidden="{ ref: 'newsletter' }"
    @complete="(detail) => console.log(detail.responseId)"
  />
</template>

Optional plugin with app-wide defaults (props win) that also registers the component globally:

import { PollYou } from '@pollyou/vue'
app.use(PollYou, { apiBase: 'https://app.pollyou.app', locale: 'de' })

Props and events

Props: surveyId (required), embedId, apiBase, mode (inline | popup | slider | fullpage), locale, theme (auto | light | dark), showResults, liveResults, identityToken, meta (object → JSON), hidden (object → hidden-<key> attributes), channel (default vue), preview, open (v-model:open). Other attributes (class, style, hidden-user-id="42", …) fall through to the element.

Events (payload = detail of the pollyou:* event): ready, start, answer, complete, close, error, plus update:open.

usePollYou()

<script setup lang="ts">
import { PollYouSurvey, usePollYou } from '@pollyou/vue'
const { survey, open, isOpen, lastEvent, completed } = usePollYou()
</script>

<template>
  <button @click="open">Feedback</button>
  <PollYouSurvey ref="survey" survey-id="AbC123xyz0" mode="popup" />
</template>

How it works

The element is rendered with h('pollyou-survey') (a plain element vnode, so the template compiler never needs to know it); attributes are applied after mounting and @pollyou/embed-core is imported lazily in onMounted. Server rendering outputs a bare <pollyou-survey> tag.

User documentation (German): docs/frameworks/vue.md.

pnpm --filter @pollyou/vue test   # Vitest + @vue/test-utils, SSR with @vue/server-renderer
pnpm --filter @pollyou/vue build  # tsdown → dist (ESM, CJS, .d.ts/.d.cts via vue-tsc)

Overlay modes and triggers

mode popup, slider or fullpage renders an overlay that is visible while open is set. Triggers (delay, scroll depth, exit intent, page views) and frequency rules come from the embed configuration (embedId); the wrapper has no trigger props – the app controls open. See @pollyou/embed-core README, "Overlay modes". Listen to pollyou:shown on the element (it bubbles) for host analytics.