firecrawl-local-dev-loop

Featured

Configure Firecrawl local development with self-hosted Docker, mocking, and testing. Use when setting up a development environment, running Firecrawl locally to save credits, or configuring test workflows with vitest. Trigger with phrases like "firecrawl dev setup", "firecrawl local development", "firecrawl docker", "firecrawl self-hosted dev", "firecrawl test setup".

AI & Automation 2,266 stars 315 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Firecrawl Local Dev Loop ## Overview Set up a fast development workflow for Firecrawl integrations. Use self-hosted Firecrawl via Docker to avoid burning API credits during development, mock the SDK for unit tests, and run integration tests against the local instance. ## Prerequisites - Node.js 18+ with npm/pnpm - Docker + Docker Compose (for self-hosted Firecrawl) - `@mendable/firecrawl-js` installed ## Instructions ### Step 1: Project Structure ``` my-firecrawl-project/ ├── src/ │ ├── scraper.ts # Firecrawl business logic │ └── config.ts # Environment-aware config ├── tests/ │ ├── scraper.test.ts # Unit tests (mocked SDK) │ └── integration.test.ts # Integration tests (real API) ├── docker-compose.yml # Self-hosted Firecrawl ├── .env.local # Dev secrets (git-ignored) ├── .env.example # Template for team └── package.json ``` ### Step 2: Self-Hosted Firecrawl for Zero-Credit Dev ```yaml # docker-compose.yml services: firecrawl: image: mendableai/firecrawl:latest ports: - "3002:3002" environment: - PORT=3002 - USE_DB_AUTHENTICATION=false - REDIS_URL=redis://redis:6379 - NUM_WORKERS_PER_QUEUE=1 - BULL_AUTH_KEY=devonly depends_on: redis: condition: service_healthy redis: image: redis:7-alpine ports: - "6379:6379" healthcheck: test: ["CMD", "redis-cli", "ping"] interval: 5s timeout: 3s retries: 5 ``` ``...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

fireflies-local-dev-loop

Configure local development workflow for Fireflies.ai GraphQL integrations. Use when setting up a development environment, mocking transcript data, or establishing a fast iteration cycle with the Fireflies API. Trigger with phrases like "fireflies dev setup", "fireflies local development", "fireflies dev environment", "develop with fireflies", "mock fireflies".

2,266 Updated today
jeremylongshore
DevOps & Infrastructure Featured

firecrawl-deploy-integration

Deploy Firecrawl integrations to Vercel, Cloud Run, and Docker platforms. Use when deploying Firecrawl-powered applications to production, configuring platform-specific secrets, or setting up self-hosted Firecrawl. Trigger with phrases like "deploy firecrawl", "firecrawl Vercel", "firecrawl production deploy", "firecrawl Cloud Run", "firecrawl Docker".

2,266 Updated today
jeremylongshore
AI & Automation Featured

firecrawl-multi-env-setup

Configure Firecrawl across development, staging, and production environments. Use when setting up multi-environment scraping pipelines, managing credit budgets per env, or configuring self-hosted Firecrawl for development. Trigger with phrases like "firecrawl environments", "firecrawl staging", "firecrawl dev prod", "firecrawl environment setup", "firecrawl config by env".

2,266 Updated today
jeremylongshore
AI & Automation Featured

flyio-local-dev-loop

Configure Fly.io local development with Docker, proxy, and SSH console. Use when setting up local dev against Fly services, testing Dockerfiles, or establishing a fast iteration cycle. Trigger: "fly.io dev setup", "fly.io local development", "fly proxy".

2,266 Updated today
jeremylongshore
AI & Automation Featured

firecrawl-ci-integration

Configure Firecrawl CI/CD integration with GitHub Actions and automated scraping tests. Use when setting up automated testing of Firecrawl integrations, configuring CI pipelines, or validating scraping behavior in pull requests. Trigger with phrases like "firecrawl CI", "firecrawl GitHub Actions", "firecrawl automated tests", "CI firecrawl", "test firecrawl in CI".

2,266 Updated today
jeremylongshore