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

@bryantocara/starter-kit

v0.1.1

Published

Shared plumbing for Bryant's Astro + Cloudflare Workers sites — SEO, lead-form to GoHighLevel, config presets, and deploy wiring. Plumbing only; never design.

Readme

@bryantocara/starter-kit

Shared plumbing for Bryant's Astro → Cloudflare Workers sites. SEO, lead capture (form → Cloudflare Turnstile → GoHighLevel), config presets, and deploy wiring — the parts that repeat on every site, in one versioned place.

Plumbing, never design. This package ships zero opinionated visual components. Every site that consumes it stays 100% custom in look and feel; it inherits only the wiring. That's what makes "individually designed, shared infrastructure" sustainable.

What's inside

| Import | What it is | |---|---| | @bryantocara/starter-kit/config | Astro config preset — Cloudflare adapter + sitemap + sensible defaults | | @bryantocara/starter-kit/components/BaseHead.astro | <head> SEO: canonical, Open Graph, Twitter cards | | @bryantocara/starter-kit/components/LeadForm.astro | Turnstile-protected lead form (bring your own markup/styles) | | @bryantocara/starter-kit/server/lead | Server handler: verify Turnstile + validate/allowlist fields → POST to a GHL inbound webhook | | @bryantocara/starter-kit/presets/gitattributes | The .gitattributes every site copies |

Using it in a site

npm install @bryantocara/starter-kit @astrojs/cloudflare
// astro.config.mjs
import { defineConfig } from 'astro/config';
import { presetConfig } from '@bryantocara/starter-kit/config';

export default defineConfig({
  ...presetConfig({ site: 'https://example.com' }),
});
// src/pages/api/lead.ts
import { handleLead } from '@bryantocara/starter-kit/server/lead';
export const prerender = false;
export const POST = handleLead;

For a form whose fields differ from the default (name, email, message), build a configured handler instead:

import { createLeadHandler } from '@bryantocara/starter-kit/server/lead';
export const POST = createLeadHandler({ fields: ['name', 'email', 'company', 'message'] });

Secrets (GHL webhook URL, Turnstile keys) are per-site environment variables — never committed, never in this package.

Per-site assets

BaseHead links /favicon.svg and /favicon.ico, and emits Open Graph / Twitter image tags only when you pass image (no broken default). Provide those files in the site's public/ directory.

Versioning & evolution

This kit is never "done." Each release adds or hardens plumbing — a new integration, a better form handler, a perf default. Sites adopt updates by bumping the version when they're ready; a delivered client site can stay pinned to an old version, untouched. Semver:

  • patch — fixes, no behavior change
  • minor — new, opt-in, backward-compatible plumbing
  • major — a change that needs site-side edits (called out in the release notes)

Status

v0.x — pre-1.0, evolving quickly while the first sites (bryant-expert onward) shake it out. The API may shift between minors until v1.0.0.

License

MIT © 2026 Bryant B. Lopes