fix(vercel): clone webpack

[avivkeller]

No description provided.

[vercel]

Deployment failed with the following error:

The `vercel.json` schema validation failed with the following message: should NOT have additional property `buildCommand:`

Learn More: https://vercel.com/docs/concepts/projects/project-configuration

[vercel]

Deployment failed with the following error:

You don't have permission to create a Preview Deployment for this Vercel project: webpack-doc-kit.

View Documentation: https://vercel.com/docs/accounts/team-members-and-roles

[ovflowd]

Fast-tracking as a hot-fix.

[Copilot]

Pull request overview

Adds a custom Vercel build step intended to run the repo’s webpack-cloning step before producing the static site output (out/) for deployment.

Changes:

• Update vercel.json to configure a custom build command that runs clone-webpack and then build.
• Minor JSON formatting change (adds a trailing comma after trailingSlash).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The GitHub Pages deploy workflow creates the out/ directory before running the doc-kit generation (mkdir out && npm run build-html). The new Vercel build command doesn’t do this; if doc-kit expects the output directory to exist, the Vercel build may fail. Consider adding mkdir -p out (or moving this into the build/build-html script) so all build paths behave consistently.

Suggested change

	"buildCommand": "node --run clone-webpack && node --run build"
	"buildCommand": "mkdir -p out && node --run clone-webpack && node --run build"

[Copilot]

The property name is "buildCommand:" (with a trailing colon), which won’t be recognized by Vercel’s config schema (expects buildCommand). As a result the custom build command will be ignored. Rename the key to buildCommand, and consider using the repo’s existing npm scripts (npm run clone-webpack && npm run build) instead of node --run ... to match CI and avoid relying on Node’s experimental --run support on Vercel.