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

@jskit-ai/rewarded-web

v0.1.150

Published

Rewarded gate client workflow with explicitly composed application delivery.

Readme

@jskit-ai/rewarded-web

Client workflow and gate UI for application-owned rewards. The package requires client.vue and an explicit client.rewarded-delivery capability. Installing it does not load an ad SDK or select a provider.

Application use

const rewarded = useRewardedRuntime();
const result = await rewarded.requireUnlock({ gateKey: "bonus", workspaceSlug });

The workflow opens a prompt before delivery. It handles existing unlocks, grants, closed sessions and unavailable delivery through the app's /rewarded/* routes. The delivery capability supplies launchReward({ providerConfig, onReady, onGranted, onClosed, onUnavailable }), returning a promise for its lifecycle. Provider configuration is opaque to the workflow. The application authorizes server grants; browser callbacks alone do not prove provider viewing.

The existing gate is app-surface-only. The installed provider mounts its host and supplies client.rewarded; direct callers use createRewardedRuntime({ launchReward }). Missing delivery fails rather than selecting Google.

Google delivery pattern

See Google rewarded delivery. Copy the adapter and provider into the application and register its provider alongside RewardedClientProvider. The example handles Publisher Tag script loading, rewarded events and slot cleanup. It accepts provider google-publisher-tag and uses the configured placement as the Google ad unit path.

V0 migration

Replace old package imports, GoogleRewarded* symbols and google-rewarded.* capabilities with the generic names. Replace useGoogleRewardedRuntime() with useRewardedRuntime() and supply delivery explicitly for direct construction. There is no compatibility fallback. The core README describes table, route and configuration migration. Install @jskit-ai/rewarded-core for server workflow ownership; the Google example remains application source.

The package manifest lists application-owned inputs in both capabilities.requires and capabilities.applicationRequires. The latter identifies who supplies them; it does not make the runtime dependency optional or provide a default.