Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add watch mode and an on-success command to vp check

未关闭
#3,218 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
bun, node.js, rust, typescript
领域
cli, tooling

调研方向

Start at the vp check command implementation and compare its options and watch behavior with vp pack; the issue does not name source files or tests. Trace how checks run and how watched files are detected, then identify where a success command could be started or restarted. Done means checks run on startup and changes, the command runs only after passing checks, and --fix does not cause redundant reruns.

由索引模型根据 Issue 内容生成。

描述

pending triage
Description

I use Vite Plus to format, lint, and type-check TypeScript scripts before running them with Node or Bun.
Currently, vp check has no watch mode or success hook, so this workflow requires a separate watcher. vp pack offers these options, but introduces a build step that isn’t needed when running TypeScript directly.

Related to #1117 and #3141.

Suggested solution

Support something like:

vp check --fix --watch --on-success "node src/main.ts"

On startup and after file changes:

  • Run the configured formatting, linting, and type checks.
  • Run or restart the command only when checks pass.
  • Avoid redundant reruns caused by --fix modifying watched files.
    It would also be useful to watch additional files, such as .env, that can affect execution without being TypeScript inputs.
Alternative

No response

Additional context

No response

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
星标
6.5k
派生
296
平均合并
1 天 12 小时
30 天内合并 PR
229

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

voidzero-dev/vite-plus 的其他 Issue

查看 voidzero-dev/vite-plus 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。