import ProjectPathArg from "/snippets/cli-args-project-path.mdx"; import CommonOptions from "/snippets/cli-options-common.mdx"; import ProjectRefOption from "/snippets/cli-options-project-ref.mdx"; import EnvFileOption from "/snippets/cli-options-env-file.mdx"; import ConfigFileOption from "/snippets/cli-options-config-file.mdx"; import SkipUpdateCheckOption from "/snippets/cli-options-skip-update-check.mdx";
This runs a server on your machine that can execute Trigger.dev tasks:
npx trigger.dev@latest devpnpm dlx trigger.dev@latest devyarn dlx trigger.dev@latest devIt will first perform an update check to prevent version mismatches, failed deploys, and other errors. You will always be prompted first.
You will see in the terminal that the server is running and listening for tasks. When you run a task, you will see it in the terminal along with a link to view it in the dashboard.
It is worth noting that each task runs in a separate Node process. This means that if you have a long-running task, it will not block other tasks from running.
Analyzes the build output and displays detailed import timings. This is useful for debugging the start times for your runs which can be caused by importing lots of code or heavy packages.These options are available on most commands.
Install the concurrently package as a dev dependency:
concurrently --raw --kill-others npm:dev:remix npm:dev:triggerThen add something like this in your package.json scripts:
"scripts": {
"dev": "concurrently --raw --kill-others npm:dev:*",
"dev:trigger": "npx trigger.dev@latest dev",
// Add your framework-specific dev script here, for example:
// "dev:next": "next dev",
// "dev:remix": "remix dev",
//...
}