repl_setup

Configure development servers and API URLs for Replit proxy iframe previews.

Updated Dec 10, 2025
One-click install
npx skills add https://github.com/KhaledMKhaled/FodaStore --skill repl-setup-khaledmkhaled
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repl_setup
Source: https://github.com/KhaledMKhaled/FodaStore/tree/main/.local/skills/repl_setup
Command: npx skills add https://github.com/KhaledMKhaled/FodaStore --skill repl-setup-khaledmkhaled

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Replit previews often show a blank page because the development server is not configured to allow the proxy iframe and because apps incorrectly bind to localhost or the wrong port, breaking frontend access and API connectivity.

Core Features & Use Cases

  • Host & port configuration: Ensures the dev server binds to 0.0.0.0 and uses port 5000 so Replit can reach it.
  • Proxy-safe frontend-to-backend connectivity: Replaces localhost API calls with the public Replit domain obtained from environment variables.
  • Framework-specific allowedHosts setup: Provides targeted configuration guidance for Angular, React/Vite, and Vue to eliminate the most common visibility failures.
  • Visibility debugging playbook: Covers restart workflow order, log checking, and rare cache-related issues to restore correct preview rendering.

Quick Start

Configure your framework to bind to 0.0.0.0 on port 5000 with allowedHosts enabled, then replace any frontend localhost API URLs with the public DOMAIN from your Replit environment so the proxy can load your app.

Frequently Asked Questions about repl_setup

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

FAQPage Schema
Why does my Replit preview show a blank page when running an Angular or Vite app?

A blank Replit preview occurs when the dev server binds to localhost instead of 0.0.0.0:5000, preventing the proxy iframe from loading the frontend. Configuring allowedHosts for Angular, Vite, or Vue resolves this visibility failure.

How do I fix frontend API connectivity failures in Replit?

To fix frontend API connectivity failures in Replit, replace localhost API URLs with the public DOMAIN environment variable. This ensures the Replit proxy can correctly route frontend requests to your backend service.

Does my Vue dev server need specific port settings to be visible in Replit?

Yes, your Vue dev server needs to bind to 0.0.0.0 on port 5000 to be visible in Replit. Enabling host checks and allowedHosts configuration allows the proxy iframe to render frontend changes correctly.

What is the best way to configure Vite allowedHosts for Replit proxy access?

The best way to configure Vite allowedHosts for Replit proxy access is to bind the server to 0.0.0.0:5000 and enable host checks. This eliminates common visibility failures when previewing React or Vite applications.

How do I debug a Replit iframe preview that is not working?

To debug a Replit iframe preview not working, follow the restart workflow order, check server logs, and clear rare cache-related issues. Ensure your dev server is bound to 0.0.0.0:5000 to restore correct preview rendering.