Skip to content

Commit 164b36e

Browse files
matt-aitkenD-K-P
authored andcommitted
Updated the new build system docs with the prerelease package
1 parent c18ff30 commit 164b36e

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

docs/guides/new-build-system-preview.mdx

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ The main features of the new build sytem are:
1818
To use the new build system, you have to update to use our preview packages. Update the `@trigger.dev/sdk` package in your package.json:
1919

2020
```json
21-
"@trigger.dev/sdk": "https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/sdk@1265"
21+
"@trigger.dev/sdk": "0.0.0-prerelease-20240823132052"
2222
```
2323

2424
You will also need to update your usage of the `trigger.dev` CLI to use the preview release. If you run the CLI via `npx` you can update to the preview release like so:
@@ -28,13 +28,13 @@ You will also need to update your usage of the `trigger.dev` CLI to use the prev
2828
npx trigger.dev@beta dev
2929

3030
# using the preview release
31-
npx https://pkg.pr.new/triggerdotdev/trigger.dev@1265 dev
31+
npx trigger.dev@0.0.0-prerelease-20240823132052 dev
3232
```
3333

3434
If you've added the `trigger.dev` CLI to your `devDependencies`, then you should update the version to point to the preview release:
3535

3636
```json
37-
"trigger.dev": "https://pkg.pr.new/triggerdotdev/trigger.dev@1265"
37+
"trigger.dev": "0.0.0-prerelease-20240823132052"
3838
```
3939

4040
Once you do that make sure you re-install your dependencies using `npm i` or the equivalent with your preferred package manager.
@@ -83,7 +83,7 @@ The `additionalFiles` option has been moved to our new build extension system.
8383
To use build extensions, you'll need to add the `@trigger.dev/build` package to your `devDependencies`:
8484

8585
```sh
86-
npm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/build@1265 -D
86+
npm add @trigger.dev/build@0.0.0-prerelease-20240823132052 -D
8787
```
8888

8989
Now you can import the `additionalFiles` build extension and use it in your `trigger.config.ts` file:
@@ -109,7 +109,7 @@ The `additionalPackages` option has been moved to our new build extension system
109109
To use build extensions, you'll need to add the `@trigger.dev/build` package to your `devDependencies`:
110110

111111
```sh
112-
npm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/build@1265 -D
112+
npm add @trigger.dev/build@0.0.0-prerelease-20240823132052 -D
113113
```
114114

115115
Now you can import the `additionalPackages` build extension and use it in your `trigger.config.ts` file:
@@ -133,7 +133,7 @@ The `resolveEnvVars` export has been moved to our new build extension system.
133133
To use build extensions, you'll need to add the `@trigger.dev/build` package to your `devDependencies`:
134134

135135
```sh
136-
npm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/build@1265 -D
136+
npm add @trigger.dev/build@0.0.0-prerelease-20240823132052 -D
137137
```
138138

139139
Now you can import the `syncEnvVars` build extension and use it in your `trigger.config.ts` file:
@@ -181,7 +181,7 @@ export default defineConfig({
181181
We've created a build extension to support using Prisma in your Trigger.dev tasks. To use this extension, you'll need to add the `@trigger.dev/build` package to your `devDependencies`:
182182

183183
```sh
184-
npm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/build@1265 -D
184+
npm add @trigger.dev/build@0.0.0-prerelease-20240823132052 -D
185185
```
186186

187187
Then you can import the `prismaExtension` build extension and use it in your `trigger.config.ts` file, passing in the path to your Prisma schema file:

0 commit comments

Comments
 (0)