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

@whichly/astro

v1.0.1

Published

Astro integration and components for Whichly variant previews.

Downloads

146

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

kapishdimakapishdima

Keywords

whichlyastrovariantsab-teststagingclient-review

Readme

@whichly/astro

Astro integration and components for Whichly variant previews.

Use Whichly in Astro marketing pages to preview alternate versions of the same page or section. Variants may contain plain Astro markup, Astro components, or hydrated islands such as React components.

Install

npm i @whichly/astro
# or
pnpm add @whichly/astro

Configure

// astro.config.mjs
import { defineConfig } from "astro/config";
import whichly from "@whichly/astro";

export default defineConfig({
  integrations: [whichly()],
});

The integration accepts optional runtime settings:

whichly({
  floating: true,
  param: "vp",
});

WhichlyBlock.astro also boots the runtime once per page when a block is present, so the picker works even if an Astro setup does not include the injected integration script in development.

Use

---
import WhichlyBlock from "@whichly/astro/components/WhichlyBlock.astro";
import WhichlyVariant from "@whichly/astro/components/WhichlyVariant.astro";
import ReactHero from "../components/ReactHero.tsx";
import AstroHero from "../components/AstroHero.astro";
---

<WhichlyBlock name="hero">
  <WhichlyVariant name="astro">
    <AstroHero />
  </WhichlyVariant>

  <WhichlyVariant name="react">
    <ReactHero client:load />
  </WhichlyVariant>
</WhichlyBlock>

The first variant is shown by default. Selecting another variant updates the URL, for example:

?vp=hero:react

This makes preview links shareable.

Important layout rule

Place WhichlyBlock / WhichlyVariant inside the document body. Do not wrap a component that emits a full <html> document or an Astro layout component that owns <html> / <body>.

Good:

<BaseLayout>
  <WhichlyBlock name="homepage">
    <WhichlyVariant name="current">
      <HomePageContent />
    </WhichlyVariant>
    <WhichlyVariant name="test">
      <h1>Hello world</h1>
    </WhichlyVariant>
  </WhichlyBlock>
</BaseLayout>

Avoid:

<WhichlyBlock name="homepage">
  <WhichlyVariant name="current">
    <FullPageWithHtmlAndBody />
  </WhichlyVariant>
</WhichlyBlock>

Astro islands

Astro islands inside inactive variants may still hydrate depending on their client:* directive. This is intentional for the initial render-all implementation and matches the React package model.