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

@byebot/svelte

v1.0.0

Published

Svelte/SvelteKit integration for Byebot

Downloads

72

Readme

@byebot/svelte

Svelte/SvelteKit integration for Byebot.

GitHub: https://github.com/ByeBot-Integrations/Svelte

Installation

npm install @byebot/svelte

Usage

Basic Form (Recommended)

The captcha token is automatically added as a hidden byebot-token field when the user completes verification.

<script>
  import { Byebot } from '@byebot/svelte';
</script>

<form action="/api/login" method="POST">
  <input name="email" type="email" />
  <input name="password" type="password" />
  <Byebot siteKey="your-site-key" />
  <button type="submit">Login</button>
</form>

With Callback (Optional)

Use on:verify if you need to know when verification completes (e.g., enable submit button).

<script lang="ts">
  import { Byebot } from '@byebot/svelte';

  let isVerified = false;

  function handleVerify(event: CustomEvent<string>) {
    console.log('Token:', event.detail);
    isVerified = true;
  }
</script>

<Byebot siteKey="your-site-key" on:verify={handleVerify} />
<button disabled={!isVerified}>Submit</button>

Server-Side Validation

Validate the byebot-token from the form submission:

// src/routes/api/login/+server.ts
import { validateByebotToken } from "@byebot/svelte/server";
import { json, error } from "@sveltejs/kit";

export const POST = async ({ request }) => {
  const formData = await request.formData();
  const token = formData.get("byebot-token") as string;

  const result = await validateByebotToken({
    apiKey: process.env.BYEBOT_API_KEY!,
    token,
  });

  if (!result.valid) {
    throw error(403, "Captcha failed");
  }

  // Captcha valid - proceed with login
  const email = formData.get("email");
  const password = formData.get("password");
  // ...

  return json({ success: true });
};

API

<Byebot />

| Prop | Type | Required | Description | | --------- | -------- | -------- | -------------------------------- | | siteKey | string | Yes | Your site key from the dashboard |

| Event | Payload | Description | | -------- | -------- | ------------------------------- | | verify | string | Emitted on verification success |

validateByebotToken(options)

| Option | Type | Required | | -------- | -------- | -------- | | apiKey | string | Yes | | token | string | Yes |

Returns: Promise<{ valid: boolean, message?: string, rawResponse?: unknown }>