@workflow/next 4.0.1-beta.69 → 4.0.1-beta.70
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/docs/api-reference/index.mdx +1 -1
- package/docs/next.mdx +5 -5
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -7,7 +7,7 @@ related:
|
|
|
7
7
|
- /docs/getting-started/next
|
|
8
8
|
---
|
|
9
9
|
|
|
10
|
-
Next.js integration for Workflow
|
|
10
|
+
Next.js integration for Workflow SDK that automatically configures bundling and runtime support.
|
|
11
11
|
|
|
12
12
|
## Functions
|
|
13
13
|
|
package/docs/next.mdx
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
title: Next.js
|
|
3
3
|
description: This guide will walk through setting up your first workflow in a Next.js app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.
|
|
4
4
|
type: guide
|
|
5
|
-
summary: Set up Workflow
|
|
5
|
+
summary: Set up Workflow SDK in a Next.js app.
|
|
6
6
|
prerequisites:
|
|
7
7
|
- /docs/getting-started
|
|
8
8
|
related:
|
|
@@ -141,7 +141,7 @@ export async function handleUserSignup(email: string) {
|
|
|
141
141
|
We'll fill in those functions next, but let's take a look at this code:
|
|
142
142
|
|
|
143
143
|
* We define a **workflow** function with the directive `"use workflow"`. Think of the workflow function as the _orchestrator_ of individual **steps**.
|
|
144
|
-
* The Workflow
|
|
144
|
+
* The Workflow SDK's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
|
|
145
145
|
|
|
146
146
|
## Create Your Workflow Steps
|
|
147
147
|
|
|
@@ -245,7 +245,7 @@ curl -X POST --json '{"email":"hello@example.com"}' http://localhost:3000/api/si
|
|
|
245
245
|
|
|
246
246
|
Check the Next.js development server logs to see your workflow execute, as well as the steps that are being processed.
|
|
247
247
|
|
|
248
|
-
Additionally, you can use the [Workflow
|
|
248
|
+
Additionally, you can use the [Workflow SDK CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
|
|
249
249
|
|
|
250
250
|
```bash
|
|
251
251
|
# Open the observability Web UI
|
|
@@ -254,11 +254,11 @@ npx workflow web
|
|
|
254
254
|
npx workflow inspect runs
|
|
255
255
|
```
|
|
256
256
|
|
|
257
|
-
|
|
258
258
|
|
|
259
259
|
## Deploying to production
|
|
260
260
|
|
|
261
|
-
Workflow
|
|
261
|
+
Workflow SDK apps currently work best when deployed to [Vercel](https://vercel.com/home) and need no special configuration.
|
|
262
262
|
|
|
263
263
|
<FluidComputeCallout />
|
|
264
264
|
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@workflow/next",
|
|
3
|
-
"version": "4.0.1-beta.
|
|
4
|
-
"description": "Next.js integration for Workflow
|
|
3
|
+
"version": "4.0.1-beta.70",
|
|
4
|
+
"description": "Next.js integration for Workflow SDK",
|
|
5
5
|
"type": "commonjs",
|
|
6
6
|
"main": "dist/index.js",
|
|
7
7
|
"files": [
|
|
@@ -29,8 +29,8 @@
|
|
|
29
29
|
"@swc/core": "1.15.3",
|
|
30
30
|
"semver": "7.7.4",
|
|
31
31
|
"watchpack": "2.5.1",
|
|
32
|
-
"@workflow/builders": "4.0.1-beta.
|
|
33
|
-
"@workflow/core": "4.2.0-beta.
|
|
32
|
+
"@workflow/builders": "4.0.1-beta.65",
|
|
33
|
+
"@workflow/core": "4.2.0-beta.74",
|
|
34
34
|
"@workflow/swc-plugin": "4.1.0-beta.21"
|
|
35
35
|
},
|
|
36
36
|
"devDependencies": {
|