The `isitme` package (currently version 0.0.7) provides a highly streamlined and zero-configuration solution for passkey-based authentication, specifically engineered for solo developers or 'solo builders'. It abstracts away the complexities of implementing WebAuthn, offering a simple 'no accounts, just your fingerprint' approach to secure access. The library facilitates both passkey registration and subsequent login flows, leveraging device-native authentication methods without the need for traditional backend user management or database integration. It offers first-class integrations with popular JavaScript frameworks such as React, Hono, Next.js, and Vue, providing framework-specific components or utilities that handle the entire passkey lifecycle. Its core differentiator lies in its extreme simplicity and developer experience, aiming for rapid integration and minimal friction for securely gating content or functionality. While in early development (pre-1.0), it focuses on providing a robust yet easy-to-use authentication layer for personalized, secure access.
npm install isitmeVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to protect a React component using the `IsItMe` wrapper. It handles passkey registration on first visit and subsequent authentication.
Pin exact versions (e.g., `npm install isitme@0.0.7`) and review release notes carefully when updating to new versions.
Always serve your application over HTTPS in production. For local development, ensure your development server is configured for HTTPS or use `localhost` directly.
Add `@import 'isitme/tailwind.css';` to your main CSS entry point, as documented in the README.
Inform users about passkey compatibility and consider providing alternative authentication methods or graceful degradation for unsupported environments if broad accessibility is critical.
Change your import statement to `import { IsItMe } from 'isitme/react';`.Ensure the user is actively consenting to the passkey prompt. Verify device settings for biometrics/security keys. Ensure your origin is considered secure (HTTPS).
Ensure your application is being served over HTTPS. If developing locally, ensure your development server is configured for HTTPS or verify you are accessing via `localhost`.