Identify and avoid FireCrawl anti-patterns and common integration mistakes.
Use when reviewing FireCrawl code for issues, onboarding new developers,
or auditing existing FireCrawl integrations for best practices violations.
Trigger with phrases like "firecrawl mistakes", "firecrawl anti-patterns",
"firecrawl pitfalls", "firecrawl what not to do", "firecrawl code review".
Identify and avoid FireCrawl anti-patterns and common integration mistakes.
Use when reviewing FireCrawl code for issues, onboarding new developers,
or auditing existing FireCrawl integrations for best practices violations.
Trigger with phrases like "firecrawl mistakes", "firecrawl anti-patterns",
"firecrawl pitfalls", "firecrawl what not to do", "firecrawl code review".
allowed-tools
Read, Grep
version
1.0.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
FireCrawl Known Pitfalls
Overview
Common mistakes and anti-patterns when integrating with FireCrawl.
// Blast requests, crash on 429for (const item of items) {
await firecrawlClient.process(item); // Will hit rate limit
}
✅ Better Approach
import pLimit from'p-limit';
const limit = pLimit(5); // Max 5 concurrentconst rateLimiter = newRateLimiter({ tokensPerSecond: 10 });
for (const item of items) {
await rateLimiter.acquire();
awaitlimit(() => firecrawlClient.process(item));
}
Pitfall #3: Leaking API Keys
❌ Anti-Pattern
// In frontend code (visible to users!)const client = newFireCrawlClient({
apiKey: 'sk_live_ACTUAL_KEY_HERE', // Anyone can see this
});
// In git history
git commit -m "add API key"// Exposed forever
const client = newFireCrawlClient({
timeout: 5000, // Too short for some operationsbaseUrl: 'https://api.firecrawl.com', // Can't change for staging
});