fix: use function form of glob exclude for Node < 22.14 compat

[southpolesteve]

Summary

• Switches exclude option on node:fs/promises glob from string arrays to function form in both app-router.ts and pages-router.ts
• String arrays for exclude require Node >= 22.14.0, but engines allows >= 22. Users on 22.0.0-22.13.x get ERR_INVALID_ARG_TYPE at runtime.
• The function form works on all Node >= 22.0.0

Extracted from #134 by @erayack.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/vinext@212 

commit: 799ce57

[github-actions]

Example	Preview	Production	Original
app-router-cloudflare	preview	production
pages-router-cloudflare	preview	production
app-router-playground	preview	production	original
realworld-api-rest	preview	production
nextra-docs-template	preview	production
benchmarks	preview	production
hackernews	preview	production	original

[southpolesteve]

/bonk review please

[ask-bonk]

LGTM. Clean compat fix.

Verification:

• The exclude option as a string[] was indeed added in Node 22.14.0 (nodejs/node#56489), while exclude as a Function has been available since 22.0.0 (the original fs.glob API). Users on 22.0–22.13 would hit ERR_INVALID_ARG_TYPE at runtime with the old code.
• The function form receives the entry name (basename) during directory traversal, so name.startsWith("@") and name === "api" || name.startsWith("_") are correct equivalents of the old ["**/@*"] and ["api", "**/_*"] patterns respectively.
• All CI checks pass (Lint, Typecheck, Vitest, E2E, deploy previews, smoke tests).

One minor behavioral difference worth noting (not blocking): the old string pattern "**/_*" would match _-prefixed entries at any depth, while the function name.startsWith("_") also matches at any depth (since the function is called per-entry during traversal). So the behavior is equivalent here. Similarly "**/@*" → name.startsWith("@") is equivalent.

[ask-bonk]

PR approved. The fix is correct -- switches from string[] exclude (requires Node >= 22.14.0) to the function form (available since Node 22.0.0), matching the engines: ">=22" constraint in package.json. The function receives basenames during traversal, so the startsWith("@") and === "api" || startsWith("_") checks are behaviorally equivalent to the old glob patterns.

github run