Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Warn on certain other tooling config files

Open
  • Is something wrong?
#2,546 1 comment 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
vite
Domain
build-system, tooling

Research direction

Start at the vp migrate entry point and inspect how existing Vite+, Vitest, tsdown, Oxlint, and Oxfmt configuration files are detected. Review the listed Jest, Rolldown, Rollup, and possible Biome migration guidance. Done means detected configurations produce the appropriate migration warnings and point users to the relevant instructions.

Written by the indexing model from the issue text.

Description

migration pending triage
Description

Currently Vite+ migrates the following first-party tool configurations automatically:

  • Vite (vite.config.ts)
  • Vitest (vitest.config.ts)
  • tsdown (tsdown.config.ts)
  • Oxlint (.oxlintrc.json)
  • Oxfmt (.oxfmtrc.json)

As well as the following third-party tool configurations:

  • ESLint (via @oxlint/migrate)
  • Prettier (via oxfmt --migrate flow)
  • tsup (via tsdown-migrate)

However, this still leaves certain tools unmigrated, which may have a Vite+-native replacement.

Suggested solution

The following tools, if they and their config files are detected in the current project, will trigger a warning during vp migrate, pointing to each respective tool's instructions for migrating where possible:

  • Jest / vite-jest -> Vitest
    • vite-jest is 5 years old so it's probably going to be harder to migrate for most people.
  • Rolldown -> Vite or tsdown
    • Most users of Rolldown directly are likely looking for something like tsdown. The Vite mention is for if the user is a frontend library developer, in which case Vite(+)'s Library Mode probably makes more sense.
  • Rollup -> Rolldown or tsdown
    • I do not believe there is a direct Rollup -> tsdown migration guide, it probably makes sense to point to Rolldown's instead, but then it runs into the above condition of migrating off of direct Rolldown usage.
  • Biome? -> oxlint/oxfmt
    • This one is a bit of a stretch considering their current plugins API is different on a fundamental level, not to mention their parser being different, so I'm probably going to drop this in the final implementation.
Alternative

Not letting the user know. This means the user might be using an entirely different set of tools which may behave differently, partially defeating the point of the unified toolchain vision of Vite+.

Additional context

I'm thinking of working on this, it's been a thing on my mind for a couple of months now.

Validations
  • Read the Contributing Guidelines.
  • Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
  • Check that there isn't already an issue requesting the same feature.
Dominant language
Rust
Stars
5.8k
Forks
267
Avg merge
20h 45m
Merged PRs (30d)
142

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from voidzero-dev/vite-plus

All issues in voidzero-dev/vite-plus

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.