Recommended Free Tools
Inngest lets a TypeScript app start background work from an event, run that work in durable steps, and pause workflows without keeping the original request open. This guide follows the official TypeScript SDK v4 documentation. Its end-to-end quick start uses Next.js App Router; if you use another framework, connect the functions with that framework’s Inngest HTTP handler instead of copying the Next.js route.
How the Inngest flow works
Your application sends a named event, Inngest matches it to a registered function, and the function runs its work as steps. You expose the function through an HTTP handler in your app; that handler lets Inngest discover and invoke the functions. Inngest describes itself as “an event-driven durable execution platform that lets you write reliable background jobs, scheduled tasks, and multi-step workflows in TypeScript without any additional infrastructure.” That is the vendor’s description, not an independent comparison or performance finding. Inngest TypeScript SDK v4 documentation
Install the SDK and create a client
Install inngest as a project dependency, then initialize one shared client with a stable application ID. The SDK documentation lists support for Node.js, Bun, Deno, and edge runtimes; confirm that your chosen runtime and framework are compatible with the handler you plan to use.
npm install inngestCreate a module such as src/inngest/client.ts:
import { Inngest } from "inngest";
export const inngest = new Inngest({ id: "my-app" });Use the same client when defining functions and registering them with your serving handler. A stable ID identifies your app in Inngest.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
Define an event-triggered function
Give the function a stable ID and declare the event name that should trigger it. The official quick start uses app/task.created. Put work that should be retried or resumed inside named step.run() calls:
import { inngest } from "./client";
export const processTask = inngest.createFunction(
{ id: "process-task" },
{ event: "app/task.created" },
async ({ event, step }) => {
const result = await step.run("process-task", async () => {
// Perform the task using event.data.
return { taskId: event.data.taskId, status: "processed" };
});
await step.sleep("wait-before-follow-up", "1s");
return result;
}
);Replace the illustrative work and data shape with those used by your app. The sample’s one-second sleep demonstrates the API; choose a duration and follow-up logic that fit your workflow.
Rank #2
- TypeScript implements a superset of syntax for strictly typed development, facilitating deep static analysis and enhanced development environment integration. The compiler translates source into standard script formats, ensuring parity across any runtime.
- TypeScript is ideal for front-end developers, full-stack engineers, and software architects who build large-scale web applications. It serves those looking to improve code excellence, reduce bugs through static checking, and maintain complex projects more.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
What a durable step changes
Inngest saves the result of a successful step.run(). If a later step fails and the function retries, previously completed steps remain saved rather than being rerun as ordinary uncheckpointed code. A thrown error in a step causes that step to retry according to the function’s retry configuration. The function reference documents four retries by default and permits configuration from zero through twenty. This checkpointing applies to work placed in steps; do not assume arbitrary code outside steps is saved or resumed in the same way. Function retries reference
When to use a pause
step.sleep() pauses the workflow for the specified duration without holding the request that originally triggered the event open. Use it when a later action must happen after a delay; it is not a replacement for putting retryable business work in a durable step. The quick start demonstrates a one-second pause and shows it in the run trace.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsServe and register the function
Defining a function is not enough: your app must expose it through Inngest’s serving handler and register it there. The official end-to-end example is for Next.js App Router and exposes the handler at /api/inngest. Use the corresponding Inngest handler for your own framework rather than copying a Next.js route into a different application.
In the Next.js App Router example, the route imports the client and function, then exports the handler’s supported HTTP methods. Follow the current framework-specific quick start for the exact import and route syntax, since handler APIs and framework integration can vary by SDK version. Inngest Next.js quick start
Send the event from your application
Once the handler serves the registered function, send the event when the relevant action occurs. The quick-start event is named app/task.created; its data should include whatever the function reads, such as the illustrative taskId above.
await inngest.send({
name: "app/task.created",
data: { taskId: "task-123" },
});The event name must match the function’s trigger. Sending a differently named event will not start this event-triggered function.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Best Value
Verify a run locally
Use the Inngest Dev Server to check the full path before deploying: start the local server, make sure your app’s Inngest handler is available to it, send the sample event, and inspect the resulting run. The getting-started guide describes the local trace UI at http://localhost:8288. Inngest getting-started guide
- Start your application and handler. Run your framework’s local development server so the registered functions can be served.
- Start the Inngest Dev Server. Follow the current local setup instructions in the getting-started guide.
- Send
app/task.created. Trigger it through the app code or the Dev Server’s available event tools, using data your function expects. - Open
http://localhost:8288. Select the run and check its event, step output, timeline, and completion state.
A successful trace should show the event that started the run, the durable step and its output, and the pause in the timeline before completion. If no run appears, first check that the event name matches the trigger and that the function is registered on the handler your app exposes. If a run appears but a step fails, inspect its recorded error and confirm the needed values are present in the event data.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
