Warn on certain other tooling config files
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- vite
- 领域
- build-system, tooling
调研方向
从 vp migrate 入口开始，检查如何检测现有的 Vite+、Vitest、tsdown、Oxlint 和 Oxfmt 配置文件。查看列出的 Jest、Rolldown、Rollup 以及可能的 Biome 迁移指南。完成的标准是：检测到的配置会生成相应的迁移警告，并引导用户查看相关说明。
由索引模型根据 Issue 内容生成。
描述
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 --migrateflow) - 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-> Vitestvite-jestis 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.
- 主要语言
- Rust
- 星标
- 6k
- 派生
- 271
- 平均合并
- 1 天 12 小时
- 30 天内合并 PR
- 198
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
voidzero-dev/vite-plus 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 70/100
voidzero-dev/vite-plus#2970 ·
维护者通常 1 天内回复
-
PowerShell `vp` wrapper hides failures: `$?` is `True` and `&&` keeps going after `vp` fails可能已有人在做 @fengmk2 于 1 天前认领。 未关闭bug pending triage
难度 2/5 1-3 小时 新手友好度 72/100
voidzero-dev/vite-plus#2934 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Skip the `vpr` hint when the script runs the same built-in可能已有人在做 @kshanxs 今天认领。 未关闭pending triage
难度 2/5 1-3 小时 新手友好度 85/100
voidzero-dev/vite-plus#2892 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
pending triage
难度 2/5 1-3 小时 新手友好度 72/100
voidzero-dev/vite-plus#2882 · 2 条评论 ·
维护者通常 1 天内回复
-
`lazyPlugins` docs: dynamic import of a local module still slows down config loading可能已有人在做 @kshanxs 今天认领。 未关闭documentation pending triage
难度 1/5 1 小时以内 新手友好度 78/100
voidzero-dev/vite-plus#2875 · 4 条评论 ·
维护者通常 1 天内回复
查看 voidzero-dev/vite-plus 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 5 天内回复
-
✨ enhancement needs-discussion
难度 1/5 1 小时以内 新手友好度 85/100
-
virtio-fs (Linux passthrough): debug log in do_lookup panics the fs worker on non-UTF-8 file names可能已有人在做 @zcl-g5 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 2 天内回复
-
area:docs documentation good first issue priority:low
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复