firecrawl / firecrawl/open-lovable

Sandbox apps render without Tailwind styles (prompt blocks config files)

Open
#130 1 comment 4 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
28.4k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Problem

When generating sandbox apps (Vercel + e2b.dev), TailwindCSS classes were included in code but styles were not applied.
The root cause is in the system prompt: it explicitly instructs to never generate tailwind.config.js or postcss.config.js.

Steps to Reproduce

1. Generate a sandbox app that uses TailwindCSS classes.
2. Deploy to sandbox (Vercel/e2b.dev).
3. The output shows plain HTML with no Tailwind styling.

Root Cause

The prompt prevents generation of essential config files:

tailwind.config.js
postcss.config.js

Without these files, Tailwind cannot process classes into CSS.

Solution

I fixed this by updating the prompt to allow and require Tailwind config files to be generated the first time.
Once these files exist, subsequent generations work fine and styles render correctly.

Suggestion

Update the system prompt to include Tailwind configs when needed.
Ensure the sandbox template always starts with these files.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.