☂️ Plan for 2026 Q4 #3277

The purpose of this plan is to provide transparency to our community and collaborators by sharing our current goals and timelines.

We will be actively working on the tasks listed below, which have been aligned with our goals for Q4 (Oct - Dec 2026).

If you see something that is not on this list but is strongly needed, please write a detailed requirement on this issue if you feel the need for feature prioritization. Also, remember this is not a complete list, so please search for relevant issues beforehand.

For broader collaboration, you can also find us on Discord.

P0: Cache Tools That Maintain Their Own Cache (@wan9chi)

Tools such as Vitest, TypeScript, and Astro read and rewrite their own cache files. Vite Task currently refuses to cache these tasks because their reads and writes overlap.

Support these patterns without requiring manual exclusions in cache.input or cache.output.

P0: Release Vite Task Remote Caching (@wan9chi)

Vite Task can cache task results without requiring users to define inputs manually. We intend it to replace Turborepo and Nx.

Test remote caching in real projects to prepare it for production. Release it publicly with a Workers-based service implementation.

P0: Run TypeScript with vpx (@fengmk2)

Make vpx index.ts work like tsx, so developers can run TypeScript scripts as part of their Vite+ workflow.

P0: Maintain an Official Homebrew Tap (@fengmk2)

Provide an official Homebrew tap for installing and upgrading Vite+. Connect the tap to the release process to keep it current.

P0: Align the Core Version with Vite (@fengmk2)

Increase the major version of @voidzero-dev/vite-plus-core to 8. Define how future versions map to bundled Vite versions.

With package aliases, compatible dependencies should pass peer dependency checks, while incompatible dependencies should still fail. This should reduce reliance on broad peerDependencyRules exceptions. See #2806.

P1: Define the Vite+ JavaScript API (@fengmk2, @wan9chi)

Design JavaScript APIs for Vite+ features beyond linting and formatting. These APIs should let developers use those features from scripts and integrations.

The initial scope remains open. First, decide which features and workflows to support. Include usage examples for the selected APIs.

For linting and formatting, keep the Oxlint and Oxfmt APIs unchanged. Change only the import paths to vite-plus/lint and vite-plus/fmt, respectively.

P1: Improve CLI Configuration Loading Performance (@fengmk2)

Reduce repeated loading of vite.config.ts to make vp check and vp staged faster. Establish performance baselines to measure the improvement. See #2698.

P1: Add Varlock Support (@fengmk2)

Define the initial scope and integration approach for Varlock. Then implement and document the feature.

P1: Support Monorepo Package Publishing (@fengmk2)

Support publishing multiple npm packages from a monorepo, including version management, internal dependency updates, and publishing order.

P1: Improve Automatic File Tracking on Linux (@wan9chi)

With remote caching, we expect more tasks to run on Linux CI. The current Linux backend fails on WSL2 and misses file reads made through direct syscalls. See vite-plus#1643 and vite-task#777.

Build a new Linux tracking backend that addresses these limitations.

P2: Address the Issue Backlog (@fengmk2)

Triage the issue backlog and remove duplicates. Prioritize problems that affect installation, migration, and daily use.

Reserve time throughout Q4 for issues that block users.

P2: Manage Older Node.js Versions (@fengmk2)

Support older releases such as Node.js 16, 18, and 20 in the version manager. Clarify the runtime requirements for user projects and for Vite+ itself.