trigger-config
Configure Trigger.dev projects with trigger.config.ts. Use when setting up build extensions for Prisma, Playwright, FFmpeg, Python, or customizing deployment settings.
Security Assessment
Detected risks:
About trigger-config
The trigger-config skill provides comprehensive guidance for configuring Trigger.dev projects through the trigger.config.ts file and build extensions system. It addresses the common challenge of integrating various tools and dependencies into serverless background job workflows, enabling developers to set up complex runtime environments without manual infrastructure configuration. This skill covers everything from basic project setup to advanced integration scenarios involving databases, browser automation, media processing, and multi-language support.
The skill's main capabilities include configuring runtime environments (Node.js or Bun), setting up retry policies, and most importantly, leveraging build extensions to integrate tools like Prisma for database operations, Playwright and Puppeteer for browser automation, FFmpeg for media processing, and Python for ML/AI workloads. It also covers environment variable synchronization, system package installation via apt-get, and including additional static files in deployments. Each extension is documented with practical code examples showing exact configuration syntax and common parameter options.
This skill is particularly valuable for backend developers building automated workflows, data processing pipelines, web scraping systems, or AI/ML processing tasks with Trigger.dev. It's essential for teams transitioning from monolithic applications to background job architectures, developers integrating multiple technologies in a single project, and anyone needing to run specialized tools (browsers, media processors, Python scripts) within serverless task environments. The skill also provides pre-configured combinations for common use cases like full-stack web applications, AI/ML processing pipelines, and web scraping systems.
FAQ
Which runtime environments does Trigger.dev support?
Trigger.dev supports Node.js (default), Node.js 22, and Bun runtimes. You can specify the runtime in trigger.config.ts using the 'runtime' property with values 'node', 'node-22', or 'bun'.
Can I use multiple build extensions together in one project?
Yes, you can combine multiple build extensions in the extensions array. Common combinations include Prisma with environment sync for full-stack apps, Python with FFmpeg for AI/ML processing, or Playwright with additional files for web scraping. Each extension operates independently and they can be stacked as needed.
How does Prisma migration work in Trigger.dev deployments?
The Prisma extension supports automatic migrations during deployment by setting migrate: true in the configuration. You must provide the schema path and can optionally specify a directUrlEnvVarName for direct database connections. Migrations run as part of the build process before tasks are deployed.
What browsers are available with the Playwright extension?
The Playwright extension supports Chromium, Firefox, and WebKit browsers. You specify which browsers to include in the configuration using the 'browsers' array, such as ['chromium'] for a single browser or ['chromium', 'firefox', 'webkit'] for all three.
How do I sync environment variables dynamically across different environments?
Use the syncEnvVars extension with an async function that receives a context object containing the current environment (dev, staging, prod). The function should return an array of environment variable objects with 'name' and 'value' properties, allowing you to fetch secrets or configure values based on the deployment environment.
Install trigger-config
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
triggerdotdev/skills