Files
triggerdotdev--trigger.dev/docs/v3/cli-dev.mdx
T
nicktrn b207601732 v3: semi-automatic package update command (#1052)
* fix package manager detection

* fix cli update check while in beta

* add update command and warn on mismatches

* update fixes and better integration with dev and deploy

* fix for ci

* update docs

* changeset

* be more specific about prompts before updates

* fail on version mismatch during ci

* update github actions docs

* fix package manager copypasta

* remove ncu

* ignore companyicons

* improve warnings and errors
2024-04-23 16:08:46 +01:00

51 lines
1.2 KiB
Plaintext

---
title: "CLI dev command"
description: "The `trigger.dev dev` command is used to run your tasks locally."
---
This runs a server on your machine that can execute Trigger.dev tasks:
<CodeGroup>
```bash npm
npx trigger.dev@beta dev
```
```bash pnpm
pnpm dlx trigger.dev@beta dev
```
```bash yarn
yarn dlx trigger.dev@beta dev
```
</CodeGroup>
It 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 requests. 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.
## Options
### Attaching a local debugger
You can use the `--debugger` flag to run the server in debug mode. This will allow you to attach a debugger to the server and debug your tasks.
<CodeGroup>
```bash npm
npx trigger.dev@beta dev --debugger
```
```bash pnpm
pnpm dlx trigger.dev@beta dev --debugger
```
```bash yarn
yarn dlx trigger.dev@beta dev --debugger
```
</CodeGroup>