Skip to content

refactor: add the vt_ prefix to unprefixed crates - #835

Merged
wan9chi merged 1 commit into
claude/rename-vt-ipc-strfrom
claude/vt-prefix-crates
Oct 12, 2026
Merged

wan9chi merged 1 commit into
claude/rename-vt-ipc-strfrom
claude/vt-prefix-crates

Conversation

@wan9chi

@wan9chi wan9chi commented Oct 12, 2026

Copy link
Copy Markdown
Member

Motivation

With this, every crate in the workspace carries one of its two prefixes, vt_ or fspy_, so a crate's name says it belongs to vite-task. Names like socket_ipc, snapshot_test or subprocess_test otherwise read like third-party crates, here and in workspaces that depend on these crates, such as vite-plus.

Renamed, along with their directories:

  • materialized_artifact, materialized_artifact_macros
  • preload_test_lib
  • pty_terminal, pty_terminal_test, pty_terminal_test_client
  • snapshot_test
  • socket_ipc
  • subprocess_test

vt and fspy are the prefixes themselves, so they keep their names. Runtime names derived from the old crate names, such as the socket_ipc_ socket prefix and the pty-terminal-test: milestone marker, stay as they are.

vite-plus depends on pty_terminal_test, pty_terminal_test_client, and snapshot_test by name, so its next vite-task bump needs to switch to the new names.

🤖 Generated with Claude Code

Rename every crate that has neither the `vt_` nor the `fspy_` prefix:

- materialized_artifact, materialized_artifact_macros
- preload_test_lib
- pty_terminal, pty_terminal_test, pty_terminal_test_client
- snapshot_test
- socket_ipc
- subprocess_test

`vt` and `fspy` keep their names. Runtime names derived from the old
crate names, such as the `socket_ipc_` socket prefix and the
`pty-terminal-test:` milestone marker, are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@wan9chi
wan9chi added this pull request to stack #836 October 12, 2026 03:55
@github-actions

Copy link
Copy Markdown

fspy benchmark

linux

dynamic/launch             change  -0.59%  [ -5.47% ..  +5.15%]  overhead   +55.40%
dynamic/access             change  +0.00%  [ -2.89% ..  +3.82%]  overhead   +23.35%
dynamic/access-relative    change  -0.54%  [ -4.73% ..  +1.99%]  overhead   +72.23%
dynamic/access-contended   change  +2.68%  [ -6.85% .. +12.90%]  overhead   +42.44%
static/launch              change  +0.27%  [ -4.74% ..  +4.91%]  overhead  +189.43%
static/access              change  +0.36%  [ -1.05% ..  +2.25%]  overhead +1449.90%
static/access-relative     change  -0.22%  [ -2.10% ..  +1.27%]  overhead +1910.27%
static/access-contended    change  +0.11%  [-12.19% ..  +9.55%]  overhead +1474.79%

macos

dynamic/launch             change  -0.62%  [ -3.92% ..  +3.07%]  overhead  +222.20%
dynamic/access             change  -0.38%  [ -5.80% ..  +3.44%]  overhead    +3.80%
dynamic/access-relative    change  +0.22%  [ -4.98% ..  +3.98%]  overhead  +228.52%
dynamic/access-contended   change  +0.24%  [ -2.70% ..  +2.03%]  overhead    +0.12%

windows

dynamic/launch             change  -0.34%  [ -7.08% ..  +8.00%]  overhead   +30.58%
dynamic/access             change  +0.40%  [ -7.86% .. +20.78%]  overhead    +2.88%
dynamic/access-relative    change  +0.77%  [ -5.24% .. +20.27%]  overhead    +1.79%
dynamic/access-contended   change  +0.49%  [ -5.66% ..  +5.20%]  overhead    +3.06%

@wan9chi
wan9chi merged commit b96f119 into main Oct 12, 2026
21 checks passed
@wan9chi
wan9chi deleted the claude/vt-prefix-crates branch October 12, 2026 04:00
wan9chi added a commit that referenced this pull request Oct 12, 2026
…837)

## Motivation

Follow-up to #835, which added the `vt_` prefix to the crates but left
two runtime names on the old crate names. With this change, the
sockets/named pipes and terminal-title markers vite-task creates match
the `vt_` crate names:

- `vt_socket_ipc` temp directory (Unix) and named pipe (Windows):
`socket_ipc_` → `vt_socket_ipc_`
- Milestone title marker emitted by `vt_pty_terminal_test_client` and
documented in the `vt_pty_terminal_test` README: `pty-terminal-test:` →
`vt-pty-terminal-test:`

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
wan9chi added a commit to voidzero-dev/vite-plus that referenced this pull request Oct 13, 2026
Bumps vite-task from `7d69d65` to `9ba4cc9`.

Changelog:
``https://github.com/voidzero-dev/vite-task/compare/7d69d6577ecf6bd83deee32186de59918a712873...9ba4cc93379cf2d7a6c7e657285bb8a00e8339dc#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed``

## Breaking changes adapted
- **Crate renames** (voidzero-dev/vite-task#835): `pty_terminal_test`,
`pty_terminal_test_client`, `snapshot_test` → `vt_pty_terminal_test`,
`vt_pty_terminal_test_client`, `vt_snapshot_test` (workspace deps, the
commented local `[patch]` section, `vp_cli_snapshots`, `vp_global_cli`).
- **Milestone marker** (voidzero-dev/vite-task#837):
`pty-terminal-test:` → `vt-pty-terminal-test:` in the Rust
(`app_target.rs`) and JS (`@voidzero-dev/prompts` `milestone.ts`)
emitters and the snapshot fixtures that emit milestones by hand.
- **`EnabledCacheConfig.remote`**: new field set to `None` (the default)
for synthesized lint/fmt/test/check cache configs.

## Docs
- `vp run` summary now shows `N/M successful`
(voidzero-dev/vite-task#821); updated the examples in
`docs/guide/run.md` and the homepage run transcripts.

## Validation
- `cargo check --workspace --all-targets`, `cargo clippy --workspace
--all-targets`, and the crate tests from the bump skill pass locally.
- PTY snapshots could not be re-recorded in my sandbox (no installed
vite-plus JS package), so I'm relying on the `CLI snapshot test` CI jobs
for any recorded-output changes and will follow up on them.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01UzozvtzdYkcqXwTHFxQVem

---
_Generated by [Claude
Code](https://claude.ai/code/session_01UzozvtzdYkcqXwTHFxQVem)_

---------

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant