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

@xcwds/plugin-offline

v0.5.0

Published

Offline support for @xcwds apps: precaching and runtime caching in the service worker, an offline fallback page, and an offline notice.

Readme

@xcwds/plugin-offline

Offline support for an @xcwds app on @xcwds/sveltekit. The integration's service worker already precaches the build and serves it from this version's cache first; this plugin tunes that strategy, keeps pages and files that weren't precached once they load, and tells the page when the browser is offline.

// xcwds.config.ts
import { defineConfig } from '@xcwds/core';
import offline from '@xcwds/plugin-offline';

export default defineConfig({
	brand,
	plugins: [offline({ exclude: ['/videos/**'] })]
});
<!-- src/routes/+layout.svelte, inside <App> -->
<script lang="ts">
	import OfflineNotice from '@xcwds/plugin-offline/OfflineNotice.svelte';
</script>

<OfflineNotice label="Offline · everything still works" />

Options

All paths are app paths, without the base path.

| Option | Default | What it does | | ---------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | precache | [] | Extra paths to precache on install, beside everything the build emits. | | exclude | [] | Globs never precached or cached at runtime (* within a segment, ** across segments). They still load from the network. | | fallback | '/404.html' | The page offline navigations get when nothing is cached for them. The default boots the app, which renders its error page. | | runtimeCaching | true | Keep same-origin 200 responses without a query string that weren't precached, so they work offline later. They live in this version's cache, so an update drops them until they load again online. |

In the page

app.network holds the browser's online state: online and subscribe(listener), which calls the listener now and on every change and returns a function that stops it. <OfflineNotice> renders it as a role="status" notice; restyle it with --xcwds-offline-bg and --xcwds-offline-fg, or render your own from app.network.

Testing

buildTestWorker from @xcwds/testing runs the real worker with this plugin; pass the build lists to precache and a network to answer what isn't cached. The e2e tests in examples/minimal load the app once, go offline, and check every page, an unknown URL and the notice.