Is it possible to build only files that have changes?

[Machineric]

Hi. A huge fan of Vite here.
Always deeply appreciate for the hard work and efforts of the maintainers and the community.

I was just wondering if I could build only files that have changes,
or at least if anyone has implemented a workaround for this idea?

I found this post (vuejs/vitepress#1991) that Evan talked about a difficulty to support this feature,
but STILL it'd be really nice to have this feature because the amount of markdown files normally increase over time which hugely affect the build time. (In my case, it used to take over few hours even for deploying a small change.)

Please know that I'm not asking to implement this feature,
but rather I'm just curious about the community's opinions on this idea.

Any suggestions or advice would appreciated in advance (as always!).
Thanks.

[Labeeb2339]

Short answer: not as a general vite build mode. A production build is a module-graph operation: changing one module can affect imports, shared chunks, tree-shaking, minification, and hashed output, so Vite cannot safely treat every source file as an independent artifact.

For iterative local work, the closest built-in option is:

vite build --watch

The current CLI docs describe --watch as rebuilding when modules change, but it should not be read as “emit only the changed file”; the build pipeline still has to determine the affected graph and output.

If the expensive part is a large Markdown site, the practical split is usually:

• use the Vite dev server while editing, since it transforms modules on demand;
• run an incremental Markdown/SSG pipeline with its own content cache, or put independent sections in separate workspace packages;
• in CI, build only the changed package/section using your workspace tool (for example, a pnpm filter) and then run the site deploy step.

So vite build --watch helps with repeated builds, but an actual changed-files-only production build generally belongs in the higher-level site generator or workspace orchestration rather than Vite itself.

References: https://vite.dev/guide/cli.html#vite-build and https://vite.dev/guide/build.html