inngest-setup

Configures Inngest durable execution in TypeScript projects with serve endpoints and workers.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aashahin/ai-skills --skill inngest-setup-aashahin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: inngest-setup
Source: https://github.com/aashahin/ai-skills/tree/main/inngest-setup
Command: npx skills add https://github.com/aashahin/ai-skills --skill inngest-setup-aashahin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires inngest.

What problem does it solve? Setting up durable execution for background jobs, webhooks, and scheduled tasks in TypeScript requires correctly wiring SDK installation, client configuration, environment variables, and framework-specific serve endpoints, where small misconfigurations cause opaque 500 errors. ## Core Features & Use Cases - Client & Environment Setup: Creates a typed Inngest client with event schemas, dev-mode flags, and signing key configuration via environment variables. - Connection Modes: Covers both HTTP serve endpoints (Next.js, Express, Hono, Fastify) and WebSocket connect-as-worker mode for long-running containers. - Local Dev Server: Guides running the inngest-cli dev server with auto-discovery, custom ports, and multi-app URLs. - Use Case: You need a retry-safe webhook handler in a Next.js app. This Skill walks you through installing the SDK, creating the client, exposing /api/inngest, and testing locally with the dev server. ## Quick Start Set up Inngest in my TypeScript Next.js project with a serve endpoint and local dev server configuration.

Frequently Asked Questions about inngest-setup

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

FAQPage Schema
How do I set up Inngest in a Next.js TypeScript project?▼

Install the inngest npm package, create a shared client with new Inngest({ id: "my-app" }), then expose a serve endpoint at /api/inngest using inngest/next. Set INNGEST_DEV=1 for local development and run the dev server with npx inngest-cli dev.

How do I run the Inngest dev server locally?▼

Run npx inngest-cli@latest dev to auto-discover your app on common ports, or pass -u http://localhost:3000/api/inngest to specify the URL manually. The dev server runs at http://localhost:8288 by default and reloads when functions change.

Why does my Inngest endpoint return a 500 internal server error?▼

This happens because Inngest v4 defaults to Cloud mode and cannot find a signing key. Set INNGEST_DEV=1 in your environment for local development, or provide INNGEST_SIGNING_KEY for production Cloud mode.

Should I use Inngest serve endpoints or connect mode?▼

Use serve endpoints (HTTP) for serverless platforms like Vercel or Lambda and existing APIs. Use connect mode (WebSocket) for long-running container environments like Kubernetes or Docker, which requires Node.js 22.4+ for WebSocket support.

Does Inngest setup work with Express and Fastify?▼

Yes, Inngest provides framework-specific serve adapters: inngest/express requires express.json({ limit: "10mb" }) middleware, and Fastify uses fastifyPlugin from inngest/fastify. Adapters also exist for Cloudflare Workers and AWS Lambda.