Skip to content

Verification Loader

A copy-paste React loading indicator for a custom access-code form built on useKnockCodes. Zero dependencies.

FeedbackUtilityfeedbackloading

Best used for Composing a fully custom verification UI that still needs the standard in-flight spinner/label.

A tiny, focused component — reach for it when composing your own verification UI from scratch.

// Usage

Minimal setup

const { state } = useKnockCodes({ expectedHash: hash });

{state === "submitting" && <VerificationLoader />}
Checking...
Installation

Add this block to your project

Recommended

npx shadcn@latest add @knock-codes/verification-loader

Also installs

  • cx (classname helper)

These install together as one atomic unit — even a presentational or read-only piece needs the full verification stack (hook, types, core) behind it to actually run.

Files created (2)

  • components/knock-codes/react/cx.ts
  • components/knock-codes/react/VerificationLoader.tsx
Other ways

GitHub shorthand

npx shadcn@latest add trivedi-vatsal/knock-codes/verification-loader

Copy the files by hand

  1. Open the Code tab in the preview above.
  2. Create each path listed below in your project and paste its contents in.
  3. Do the same for anything listed under “Also installs”, if present.
// Props

API reference

PropTypeDefaultDescription
labelstring"Checking..."Text next to the spinner.
classNamestringExtra classes on the container.
Notes

Accessibility

role="status" + aria-live="polite", with the spinner itself marked aria-hidden so screen readers announce the text label once, not a decorative glyph.

Customization

The same visual `<PinInput>` shows inline via its `submitting` state, exposed standalone for a fully custom access-code form built directly on `useKnockCodes` where you're not using `<PinInput>` at all.

Security & Verification

Need a hash? Use the hash generator on Getting Started — computed locally, never sent anywhere.

The honest version

Knock Codes stops casual visitors, search engines, and forwarded links. Local mode does not stop anyone who opens DevTools — the hash ships in your client bundle by design. Server mode (swap one prop) hides the hash from the client; children you already bundled are still in the JavaScript, and a forged session works unless you wire validateSession. A velvet rope, with an optional real lock. Never marketed as more than that.

// Compose with

Blocks that pair well with this one

These combine naturally with this block, whether as a shared shell, a shared session, or a common fallback.