Eric Allam
cf13fbdf32
* Add triggerAndWait().unwrap() to more easily get at the output or throw the subtask error * Add taskId and runId to SubtaskUnwrapError * WIP docs update beta -> latest * trigger.dev init now adds @trigger.dev/build to devDependencies * How it works doc * Restructure some docs and update the cli commands * Config file docs, plus aptGet and ffmpeg extensions * Update to latest from beta docs * Add runtime to templates * Add --runtime option to the init CLI command * A bunch more doc updates after feedback * Document triggerAndWait with unwrap and result types * beta -> latest in the webapp * CLI update check no longer references beta * Add major release * Leave changeset beta, back to normal package release * Fixed default dirs option in init command * exclude windows-yarn variation of cli e2e tests because it’s buggy * Remove cache to try and fix yarn e2e test workflow errors
48 lines
1.0 KiB
Plaintext
48 lines
1.0 KiB
Plaintext
Run your Next.js app:
|
|
|
|
<CodeGroup>
|
|
|
|
```bash npm
|
|
npm run dev
|
|
```
|
|
|
|
```bash pnpm
|
|
pnpm run dev
|
|
```
|
|
|
|
```bash yarn
|
|
yarn dev
|
|
```
|
|
|
|
</CodeGroup>
|
|
|
|
Run the dev server from Step 2. of the [Initial Setup](/guides/frameworks/nextjs#initial-setup) section above if it's not already running:
|
|
|
|
<CodeGroup>
|
|
|
|
```bash npm
|
|
npx trigger.dev@latest dev
|
|
```
|
|
|
|
```bash pnpm
|
|
pnpm dlx trigger.dev@latest dev
|
|
```
|
|
|
|
```bash yarn
|
|
yarn dlx trigger.dev@latest dev
|
|
```
|
|
|
|
</CodeGroup>
|
|
|
|
Now visit the URL in your browser to trigger the task. Ensure the port number is the same as the one you're running your Next.js app on. For example, if you're running your Next.js app on port 3000, visit:
|
|
|
|
```bash
|
|
http://localhost:3000/api/hello-world
|
|
```
|
|
|
|
You should see the CLI log the task run with a link to view the logs in the dashboard.
|
|
|
|
|
|
|
|
Visit the [Trigger.dev dashboard](https://cloud.trigger.dev) to see your run.
|