Vercel doesn't cache Docusaurus Build Caches

[anaclumos]

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Prerequisites

• I'm using the latest version of Docusaurus.
• I have tried the npm run clear or yarn clear command.
• I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
• I have tried creating a repro with https://new.docusaurus.io.
• I have read the console error message carefully (if applicable).

Description

I've noticed that Vercel doesn't cache Docusaurus's .docusaurus folder or build output dir.

This is more of a Vercel problem, but I still wanted to raise the issue and add support to Vercel on this matter.

Reproducible demo

No response

Steps to reproduce

Create a deployment on Vercel.

Expected behavior

Only diff'ed files should rebuild.

Actual behavior

Each deployment on Vercel will build from scratch.

Your environment

No response

Self-service

• I'd be willing to fix this bug myself.

[anaclumos]

I created a Vercel support case regarding this matter. I will post updates as they become available.

[slorber]

Thanks

To be honest, we don't need to cache build or .docusaurus atm, and the only cache we use is node_modules/.cache (for Rspack/Webpack persistent cache).

We don't cache build and .docusaurus: these folders are automatically cleared when you start a new production build, so restoring them will not provide any benefit.

---

If you are in touch with their support, that would be cool to ensure node_modules/.cache is cached properly.

Also, their Docusaurus framework presets are Docusaurus (v1) and Docusaurus (v2).

We are on Docusaurus v3 now, they should probably rename these to something like Docusaurus (Legacy v1) and Docusaurus (v2+)

Or simply remove the old v1 option and just use Docusaurus.
V1 is not widely used anymore, and I'm not even sure how v1 is configured differently from v2.