[WIP] Test new custom Vercel middleware integration on docs

[psd-coder]

This pull request introduces two major integrations to the Astro project:

• Custom Vercel middleware generator. It replaces our custom scripts pipeline and tightly integrated with Astro's lifecycle.
• Replaces matcher generation script with one more Astro integration.

How it works

• New build method is provided as custom Astro middleware integration. During build time it compiles Astro middleware (not the custom one, as we had before) into Vercel output format, but since we could have any middleware (not only i18n) then matcher check was moved into i18n middleware itself.
• By default, middleware processes any request to the application, but we limit it to ignore static asset files.
• generate-middleware-matcher.js was transformed into one more additional Astro integration. It allows running it in Astro lifecycle: when you update any route-dependant files it automatically regenerates output file. Astro integration fails if you use dynamic imports inside it (something related to Vite), so everything we imported before just in the place now we have to pass as integration options.
• All middlewares were converted into Astro middleware format.
• Since we build website into static there is extra check in the i18n middleware whether it is called during build. Headers and cookies are empty when ctx.isPrerendered === true. It works well when the app is deployed.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
aptos-docs	Ready	Preview	Comment	Sep 9, 2025 5:52pm