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

@slashfi/elements

v0.0.1

Published

Client SDK for confirming a Slash PaymentIntent.

Readme

@slashfi/elements

Framework-agnostic public contracts for confirming a Slash PaymentIntent. The vanilla client is not implemented yet.

React merchants should use @slashfi/elements-react, which provides PaymentProvider, PaymentElement, BrandingElement, and usePaymentElements() on top of these shared contracts.

The PaymentIntent creation and client-secret routes required by the proposed SDK flow are not yet part of the published Slash API.

The React SDK confirms Whop-backed intents through POST /acquiring/client/whop/confirm. A successful response requires nextAction: { whopClientSecret: string }. Whop Elements consumes the client secret. After a failed or dismissed buyer step, the server checks the current authorization and fetches fresh Whop status outside the transaction, then locks and rechecks that the same payment still owns the intent. Whop canceled, requires_action, or requires_confirmation with a non-null last_payment_error permits release for retry. Redirects, other provider statuses, and API errors never release.

The low-level confirm request requires name and stateHash. The React SDK sends the merchant-collected cardholder name and the hash returned by bootstrap.

PaymentResult returns either error or processing (buyer done or redirected, not a settlement guarantee). Validation, payment, request, and API failures are returned as structured PaymentError values.

const result = await paymentState.confirm({ email, name, billingAddress });
if (result.type === 'error') {
  showCheckoutError(result.error.message);
} else {
  redirectToProcessingPage(result.paymentIntentId);
}

The React SDK calls handleNextAction sequentially with a 500ms delay between polls and no total timeout. It waits through confirming and requires_confirmation without a payment error. succeeded, processing, and requires_capture complete the buyer step; capture/settlement remains server-side. Failures and dismissed modals use server-verified release: pending permits retry, while any other status remains non-retryable. A redirect never releases. See the React README for the full flow.