James Ritchie
e19bf2abaf
* Format the machine override example code * Adds note to add `fluent-ffmpeg` to external * Updates onFailure with more clarification * Adds debugging in vs code to Troubleshooting * Removed link
21 lines
681 B
Plaintext
21 lines
681 B
Plaintext
Debugging your task code in `dev` is supported via VS Code, without having to pass in any additional flags. Create a launch configuration in `.vscode/launch.json`:
|
|
|
|
```json launch.json
|
|
{
|
|
"version": "0.2.0",
|
|
"configurations": [
|
|
{
|
|
"name": "Trigger.dev: Dev",
|
|
"type": "node",
|
|
"request": "launch",
|
|
"cwd": "${workspaceFolder}",
|
|
"runtimeExecutable": "npx",
|
|
"runtimeArgs": ["trigger.dev@latest", "dev"],
|
|
"skipFiles": ["<node_internals>/**"],
|
|
"sourceMaps": true
|
|
}
|
|
]
|
|
}
|
|
```
|
|
|
|
Then you can start debugging your tasks code by selecting the `Trigger.dev: Dev` configuration in the debug panel, and set breakpoints in your tasks code. |