Skip to content

Commit a93bad8

Browse files
committed
Docs upgrade guide package version. Need to use exact packages for the CLI to work
1 parent 748b48a commit a93bad8

File tree

1 file changed

+5
-16
lines changed

1 file changed

+5
-16
lines changed

docs/upgrade-to-v4.mdx

Lines changed: 5 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -471,19 +471,21 @@ To opt-in to using v4, you will need to update your dependencies to the latest v
471471
<CodeGroup>
472472

473473
```bash npm
474-
npm add @trigger.dev/sdk@v4-beta
474+
npm add @trigger.dev/sdk@v4-beta -E
475475
```
476476

477477
```bash yarn
478-
yarn add @trigger.dev/sdk@v4-beta
478+
yarn add @trigger.dev/sdk@v4-beta -E
479479
```
480480

481481
```bash pnpm
482-
pnpm add @trigger.dev/sdk@v4-beta
482+
pnpm add @trigger.dev/sdk@v4-beta -E
483483
```
484484

485485
</CodeGroup>
486486

487+
<Note> You will need to do this for all your `@trigger.dev/*` packages. </Note>
488+
487489
You'll also need to use the `v4-beta` version of the `trigger.dev` CLI package:
488490

489491
<CodeGroup>
@@ -502,19 +504,6 @@ pnpm dlx trigger.dev@v4-beta dev
502504

503505
</CodeGroup>
504506

505-
Or you could install the CLI into your `devDependencies` and then use the `trigger` binary:
506-
507-
```json package.json
508-
{
509-
"devDependencies": {
510-
"trigger.dev": "v4-beta"
511-
},
512-
"scripts": {
513-
"dev": "trigger dev"
514-
}
515-
}
516-
```
517-
518507
## Known issues
519508

520509
During the beta we will be tracking issues and releasing regular fixes.

0 commit comments

Comments
 (0)