@vercel/build-utils 13.27.1 → 13.28.0
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/CHANGELOG.md +17 -0
- package/dist/index.d.ts +1 -0
- package/dist/index.js +356 -157
- package/dist/max-duration.d.ts +44 -0
- package/dist/max-duration.js +54 -0
- package/dist/node-entrypoint.d.ts +8 -7
- package/dist/node-entrypoint.js +49 -20
- package/dist/prerender.d.ts +9 -1
- package/dist/prerender.js +8 -1
- package/dist/schemas.d.ts +1 -3
- package/dist/schemas.js +2 -6
- package/dist/strip-comments-and-literals.d.ts +16 -0
- package/dist/strip-comments-and-literals.js +39 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,22 @@
|
|
|
1
1
|
# @vercel/build-utils
|
|
2
2
|
|
|
3
|
+
## 13.28.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- 4e849dd: Add a per-route `hasPostponed` signal to `Prerender`.
|
|
8
|
+
|
|
9
|
+
`@vercel/build-utils` exposes a new optional `hasPostponed?: boolean` field on `Prerender` / `PrerenderOptions`. It is a tri-state: `true` when the route's `.meta` postponed state is present (React suspended during the build-time prerender), `false` when the framework prerendered a Prerender route without postponing, and `undefined` when the framework did not provide the signal.
|
|
10
|
+
|
|
11
|
+
`@vercel/next` populates it for app-router PPR routes (computed from the route's postponed state) and leaves it `undefined` for pages-router and other non-app-router prerenders. This is an additive, finer-grained signal — it does not change the existing `chain` / `experimentalStreamingLambdaPath` behavior — so downstream consumers can distinguish a route that actually postponed from one that has PPR machinery but fully prerendered (e.g. under `cacheComponents: true`).
|
|
12
|
+
|
|
13
|
+
## 13.27.2
|
|
14
|
+
|
|
15
|
+
### Patch Changes
|
|
16
|
+
|
|
17
|
+
- c5eeb30: Gate the client-side 900-second `maxDuration` upper bound behind the `VERCEL_CLI_SKIP_MAX_DURATION_LIMIT` environment variable. The limit is now owned by a single helper in `@vercel/build-utils` instead of being hardcoded in multiple validators. When the variable is set to `1`, the client-side maximum is skipped and validation defers to the server. Default behavior is unchanged — the maximum, the lower bound, and the integer check are all still enforced when the variable is unset.
|
|
18
|
+
- 09c39af: Fix Node.js API entrypoint detection dropping functions whose source contains comment-like sequences (`/*`, `//`, `*/`) inside string, template, or regex literals — for example an `Accept: */*` header. Handler exports are now identified with the ES/CJS module lexers instead of stripping comments with regexes, so the contents of literals are never mistaken for comments.
|
|
19
|
+
|
|
3
20
|
## 13.27.1
|
|
4
21
|
|
|
5
22
|
### Patch Changes
|
package/dist/index.d.ts
CHANGED
|
@@ -27,6 +27,7 @@ export { normalizePath } from './fs/normalize-path';
|
|
|
27
27
|
export { getOsRelease, getProvidedRuntime } from './os';
|
|
28
28
|
export * from './should-serve';
|
|
29
29
|
export * from './schemas';
|
|
30
|
+
export { DEFAULT_MAX_DURATION_LIMIT, SKIP_MAX_DURATION_LIMIT_ENV, getMaxDurationLimit, getMaxDurationSchema, } from './max-duration';
|
|
30
31
|
export * from './package-manifest';
|
|
31
32
|
export { generateProjectManifest } from './node-diagnostics';
|
|
32
33
|
export * from './types';
|