replit-auth

Authenticate users with Replit OpenID Connect PKCE in a pnpm monorepo.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/akhilksap2026/YMSNOW27032026 --skill replit-auth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: replit-auth
Source: https://github.com/akhilksap2026/YMSNOW27032026/tree/main/replit/.local/skills/replit-auth
Command: npx skills add https://github.com/akhilksap2026/YMSNOW27032026 --skill replit-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrate Replit OpenID Connect (PKCE) authentication into a pnpm monorepo (Express server, React web, and optional Expo mobile) with server-side session management and provider-driven auth flows.

Core Features & Use Cases

  • Web and mobile authentication using Replit's OIDC PKCE flow, including login, callback, and logout routes.
  • Server-side user session handling with PostgreSQL-backed sessions and user upsert in a shared monorepo.
  • Optional web and mobile client hooks and templates to bootstrap a complete auth experience.

Quick Start

Install and wire the provided server, web, and mobile components to enable Replit OpenID Connect PKCE authentication across your pnpm workspace.

Frequently Asked Questions about replit-auth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement Replit OIDC authentication in a pnpm monorepo?

Replit OIDC authentication in a pnpm monorepo is implemented via the PKCE flow across an Express server, React web client, and optional Expo mobile app. It covers browser login, callback handling, and mobile token exchange for consistent user auth state.

How does PKCE session management work with Express and React?

PKCE session management with Express and React works by handling login and callback routes on the Express server, storing sessions in PostgreSQL, and using safe cookie handling to protect user sessions while maintaining auth state in the React client.

Can I use Replit OpenID Connect with an Expo mobile app?

Yes, Replit OpenID Connect works with an optional Expo mobile app by handling mobile token exchange and providing reusable web and mobile client hooks to bootstrap a complete, consistent auth experience across platforms.

Do I need PostgreSQL to handle Replit OIDC user sessions?

Yes, PostgreSQL is required for Replit OIDC user sessions because the implementation uses a PostgreSQL-backed session store to securely manage server-side user sessions and perform user upserts in the shared monorepo.

What is the best way to secure user authentication across web and mobile clients?

The best way to secure user authentication across web and mobile clients is using an OIDC PKCE flow with an OpenID provider, loading OIDC config safely, and applying safe cookie handling to protect server-side PostgreSQL-backed sessions.