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

@deltabreen/help-vue

v0.1.0

Published

Help by DeltaBreen for Vue 3 and Nuxt: a helpdesk on your own site. The support form, a logged-in user's own tickets, the Help button and help articles as components, over Help's hosted script.

Readme

Help by DeltaBreen for Vue

A helpdesk on your own site: the support form, a logged-in user's own tickets, the Help button and your help articles as Vue components, for Vue 3 and Nuxt. They draw Help's own elements and load our hosted script once, so your site gets our fixes without a release of yours. No dependencies besides Vue.

npm install @deltabreen/help-vue

The form

// main.js
import { createApp } from 'vue'
import { createDeltaHelp } from '@deltabreen/help-vue'
import App from './App.vue'

createApp(App).use(createDeltaHelp({ siteKey: 'pk_live_…' })).mount('#app')
<!-- Support.vue -->
<script setup>
import { SupportForm } from '@deltabreen/help-vue'
</script>

<template>
  <SupportForm subject="Book a call" :fields="{ order_id: 'A-100' }" @sent="({ number }) => console.log(number)" />
</template>

Your site's key is on its Install tab in the portal. Use the test key (pk_test_…) while you try things out: it works on any page, localhost too. The live key works only on your site's verified domains and its test domains.

| Component | Element | Props beside accent, labels, lang, site-key | Events | |---|---|---|---| | SupportForm | <db-help-form> | subject (on its own, or words to start it with), :suggest="false", fields, login, thanks | sent, error, article, answered | | MyTickets | <db-help-tickets> | login | replied, closed (they marked one solved), rated, unread, view (the ticket open in it, null for the list) | | HelpButton | <db-help-launcher> | position="left", login | sent, unread | | HelpArticles | <db-help-articles> | section, inline, contact | article, answered |

Each event is the element's help:… event, with its detail as the argument. class and style go on the element itself. labels takes any of the element's words by name, as { title: 'Talk to us', emailHint: 'Your work email' }; the names are in the embed's guide.

login is where "Log in to send a message" and "Log in to see your tickets" lead, on a site that takes messages only from logged-in users: your login page, best with a way back (login="/login?return=/support"). thanks is your own thank-you page, opened once a message is sent; {number} in it becomes the ticket's number.

Nuxt

// plugins/deltahelp.js
import { createDeltaHelp } from '@deltabreen/help-vue'

export default defineNuxtPlugin((nuxtApp) => {
  nuxtApp.vueApp.use(createDeltaHelp({ siteKey: 'pk_live_…' }))
})

Then use the components in any page. On the server each draws an empty place, and the script loads in the browser.

For Vue 3.3 and later. On 3.3 and 3.4 an app that is unmounted keeps waiting for the script, which matters only on a page that mounts a second app with Help after it.

Logged-in users

Your server signs a short token that says who is logged in, with the secret from your site's Install tab (see @deltabreen/help-server). Give the plugin an address on your own site that answers with it, and 204 for a guest:

createDeltaHelp({ siteKey: 'pk_live_…', identityUrl: '/help-token' })

Or hand it over yourself when someone logs in or out:

const help = useDeltaHelp()
help.identify(() => fetch('/help-token').then((r) => r.text()))   // asked each time the form needs a fresh token
help.identify(null)                                                // logged out

Without the form

import { useDeltaHelp, useUnread } from '@deltabreen/help-vue'

const help = useDeltaHelp()
const api = await help.ready                // the script's API once it has started
await api.submit({ email, body })           // rejects with a HelpError that has a stable `code`
const unread = useUnread()                  // a ref: replies the logged-in user hasn't read

help.api is a ref that is null until the script has started. context and fields on the plugin, or help.setContext and help.setFields, are facts for your team, and values for the form's own fields on every form.

Proving your domain

Check your site on the Install tab reads your home page as your server sends it, before any script runs. A component adds nothing there, so put the <meta name="deltabreen-help" content="…"> line from the Install tab in index.html (in Nuxt, app.head in nuxt.config), or use the DNS record or the file from the same step.

Content-Security-Policy

script-src  https://help.deltabreen.eu
connect-src https://help.deltabreen.eu