@workflow/next 5.0.0-beta.20 → 5.0.0-beta.22

package/docs/api-reference/with-workflow.mdx

@@ -36,6 +36,30 @@ Remove that package from `serverExternalPackages` in your
 `next.config` to silence the warning.
 </Callout>
 
+### Workflow Discovery in Next.js
+
+`withWorkflow()` discovers workflows by scanning your Next.js entrypoints — App
+Router `route`, `page`, and `layout` files (under `app/` or `src/app/`) and any
+file under `pages/` or `src/pages/` — for `start()` calls imported from
+`workflow/api`. The workflow and step files themselves can live anywhere (for
+example `src/workflows/`); they are discovered transitively through imports, as
+long as a `start()` call in an entrypoint statically reaches them.
+
+<Callout type="info">
+Call `start()` from server-side entrypoints, including Route Handlers and Server
+Actions. Don't call workflow functions directly — that bypasses the workflow
+runtime.
+</Callout>
+
+### Next.js Server Actions and `"use server"`
+
+Don't put a top-level `"use server"` directive in modules imported by workflow
+or step functions. Workflow transformation wraps imported modules in synchronous
+initializers, and Next.js rejects a `"use server"` directive inside that wrapper
+with errors like `Server Actions must be async functions`. Keep `"use server"`
+on the files that define your Server Actions, and move shared logic into
+separate modules that don't carry the directive.
+
 ### Monorepos and Workspace Imports
 
 By default, Next.js detects the correct workspace root automatically. If your Next.js app lives in a subdirectory such as `apps/web` and workspace resolution is not working correctly, you can set `outputFileTracingRoot` as a workaround:
@@ -68,7 +92,6 @@ const nextConfig: NextConfig = {};
 
 export default withWorkflow(nextConfig, {
   workflows: {
-    lazyDiscovery: false,
     local: {
       port: 4000,
     },
@@ -79,7 +102,6 @@ export default withWorkflow(nextConfig, {
 
 | Option | Type | Default | Description |
 | --- | --- | --- | --- |
-| `workflows.lazyDiscovery` | `boolean` | `true` | Defers workflow discovery until files are requested instead of scanning eagerly at startup. Set to `false` to force eager discovery (scanning the project up front). Requires a Next.js version that supports deferred entries; older versions fall back to eager discovery automatically. |
 | `workflows.local.port` | `number` | — | Overrides the `PORT` environment variable for local development. Has no effect when deployed to Vercel. |
 | `workflows.sourcemap` | `boolean \| 'inline' \| 'linked' \| 'external' \| 'both'` | `'inline'` (dev) / `false` (prod) | Controls source maps on generated workflow bundles. See [Source maps](#source-maps) below. |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@workflow/next",
-  "version": "5.0.0-beta.20",
+  "version": "5.0.0-beta.22",
   "description": "Next.js integration for Workflow SDK",
   "type": "commonjs",
   "main": "dist/index.js",
@@ -29,8 +29,8 @@
     "@swc/core": "1.15.3",
     "semver": "7.7.4",
     "watchpack": "2.5.1",
-    "@workflow/builders": "5.0.0-beta.20",
-    "@workflow/core": "5.0.0-beta.20",
+    "@workflow/builders": "5.0.0-beta.22",
+    "@workflow/core": "5.0.0-beta.22",
     "@workflow/swc-plugin": "5.0.0-beta.5"
   },
   "devDependencies": {
@@ -38,6 +38,7 @@
     "@types/semver": "7.7.1",
     "@types/watchpack": "2.4.4",
     "next": "16.2.1",
+    "vitest": "^4.0.18",
     "@workflow/tsconfig": "5.0.0-beta.0"
   },
   "peerDependencies": {
@@ -51,6 +52,7 @@
   "scripts": {
     "build": "tsc",
     "dev": "tsc --watch",
+    "test": "vitest run src",
     "clean": "tsc --build --clean && rm -rf dist docs"
   }
 }

package/dist/builder-deferred.d.ts

@@ -1,2 +0,0 @@
-export declare function getNextBuilderDeferred(): Promise<any>;
-//# sourceMappingURL=builder-deferred.d.ts.map

package/dist/builder-deferred.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"builder-deferred.d.ts","sourceRoot":"","sources":["../src/builder-deferred.ts"],"names":[],"mappings":"AAyCA,wBAAsB,sBAAsB,iBAiiE3C"}