Skip to content

Commit 82f1b55

Browse files
only21milclaude
andcommitted
Merge main (24c063a) into r13/a070-keep-project-name-edits-open-during-ime-
Co-Authored-By: Claude Opus 5.5 <[email protected]>
2 parents 35f710c + 24c063a commit 82f1b55

561 files changed

Lines changed: 18661 additions & 9714 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.devcontainer/devcontainer.json‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
// Dev container for T3 Code. Mirrors CI (ubuntu-24.04, Node 24, Rust stable)
1+
// Dev container for T3 Code. Mirrors CI (ubuntu-24.04, Node 26, Rust stable)
22
// and the canonical setup in docs/operations/development.md: global `vp`, `vp i`.
33
// Contributor doc: docs/internals/devcontainer.md
44
{
@@ -8,7 +8,7 @@
88
// nodeGypDependencies (default true) brings python3/make/g++, which Linux
99
// needs for node-pty's node-gyp fallback (its prebuilds are mac/win only).
1010
"ghcr.io/devcontainers/features/node:2": {
11-
"version": "24"
11+
"version": "26"
1212
},
1313
// native/resource-monitor (edition 2024, needs stable >= 1.85). The server
1414
// degrades gracefully without the binary, but CI checks cargo fmt + test.

‎.github/actions/setup-ci-deps/action.yml‎

Lines changed: 19 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,22 +3,38 @@ description: Install Vite+ and the workspace dependencies from cache.
33
runs:
44
using: composite
55
steps:
6-
# setup-vp reuses an installed exact version, so restoring its home skips the
7-
# installer download on every job.
6+
# ~/.vite-plus holds vp, the Node.js runtime, and pnpm. A cache entry never
7+
# updates, so the key names all three versions; otherwise a pnpm or Node.js
8+
# bump makes every job download them from npm again.
89
- name: Resolve Vite+ version
910
id: vp
1011
shell: bash
1112
run: |
1213
echo "version=$(sed -nE 's/^ vite-plus: ([0-9][^ ]*)$/\1/p' pnpm-workspace.yaml)" >> "$GITHUB_OUTPUT"
14+
echo "node=$(jq -r '.engines.node' package.json)" >> "$GITHUB_OUTPUT"
15+
echo "pnpm=$(jq -r '.packageManager' package.json)" >> "$GITHUB_OUTPUT"
1316
1417
- name: Cache Vite+
18+
id: vp_cache
1519
if: steps.vp.outputs.version != ''
1620
uses: actions/cache@v6
1721
with:
1822
path: ~/.vite-plus
19-
key: vite-plus-home-v1-${{ runner.os }}-${{ runner.arch }}-${{ steps.vp.outputs.version }}
23+
key: vite-plus-home-v2-${{ runner.os }}-${{ runner.arch }}-${{ steps.vp.outputs.version }}-node${{ steps.vp.outputs.node }}-${{ steps.vp.outputs.pnpm }}
24+
25+
# setup-vp always runs the installer, which fetches vp from npm even when
26+
# this exact version is installed. A cache hit already has everything, so
27+
# skip setup-vp and do its remaining work here. This keeps npm outages from
28+
# failing jobs.
29+
- name: Use cached Vite+
30+
if: steps.vp_cache.outputs.cache-hit == 'true'
31+
shell: bash
32+
run: |
33+
echo "$HOME/.vite-plus/bin" >> "$GITHUB_PATH"
34+
"$HOME/.vite-plus/bin/vp" env use "${{ steps.vp.outputs.node }}"
2035
2136
- name: Setup Vite+
37+
if: steps.vp_cache.outputs.cache-hit != 'true'
2238
uses: voidzero-dev/setup-vp@v1
2339
with:
2440
node-version-file: package.json

‎.github/workflows/mobile-showcase-screenshots.yml‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ env:
4343

4444
jobs:
4545
ios:
46-
name: iPhone 6.9, iPhone 6.5, and iPad 13
46+
name: iPhone, iPhone Duo, and iPad 13
4747
if: inputs.platform == 'all' || inputs.platform == 'ios'
4848
runs-on: blacksmith-12vcpu-macos-26
4949
# Capturing every palette multiplies the device matrix by six, and only the
@@ -87,6 +87,9 @@ jobs:
8787
brew install cameroncooke/axe/axe
8888
axe --version
8989
90+
- name: Install foldable simulator controls
91+
run: npm install --global [email protected]
92+
9093
- name: Capture iOS showcase
9194
run: pnpm screenshots:mobile --platform ios --appearance "${{ inputs.appearance }}" --theme "${{ inputs.theme }}"
9295

‎.github/workflows/release-desktop.yml‎

Lines changed: 3 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -253,18 +253,13 @@ jobs:
253253
if [[ "${{ inputs.version }}" =~ -nightly\.[0-9]{8}\.[0-9]+$ ]]; then brand=nightly; fi
254254
node scripts/apply-web-brand-assets.ts "$brand" apps/server/dist/client
255255
256-
# The single-executable is built with a Node that supports --build-sea
257-
# (25.7+); the repo itself stays on the engines.node version. A native
258-
# build injects into the runner's own Node; a Windows target downloads its
259-
# node.exe.
256+
# Setup Vite+ selects the exact engines.node version from package.json.
257+
# Native builds embed that executable; cross-target builds download the
258+
# same version for their target.
260259
- name: Build CLI single-executable
261260
if: inputs.cli_archive
262261
shell: bash
263262
env:
264-
# The exact version, not a major: vp downloads it from nodejs.org/dist on
265-
# the runner, and only exact versions have a dist directory. Keep in
266-
# step with SEA_NODE_VERSION in apps/server/vite.config.ts.
267-
VP_NODE_VERSION: "26.8.2"
268263
# The executable bundles the server again, so it needs the same stamp
269264
# as release.yml's JS bundle.
270265
T3CODE_TELEMETRY_CHANNEL: ${{ github.repository == 'pingdotgg/t3code' && inputs.release_channel || 'dev' }}

‎.pnpmfile.cjs‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,15 @@
55
// Release scripts stage their own installs with explicit architectures.
66
module.exports = {
77
hooks: {
8+
// `typescript` is @tsc-rs/typescript (the catalog entry). Its npm version (0.8.x) is outside
9+
// vite-plus-core's typescript peer range, so pnpm gave the vite-plus that @effect/vitest
10+
// imports apps/marketing's [email protected] instead, and tests loaded a second vitest.
11+
readPackage(pkg) {
12+
if (pkg.name === "@voidzero-dev/vite-plus-core" && pkg.peerDependencies?.typescript) {
13+
pkg.peerDependencies.typescript = "*";
14+
}
15+
return pkg;
16+
},
817
updateConfig(config) {
918
// oxlint-disable-next-line t3code/no-global-process-runtime -- pnpm loads this file before any Effect runtime exists.
1019
if (process.platform !== "win32") return config;

‎AGENTS.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ An empty database is a bad test. Seed your worktree's `.t3` with a copy of real
100100

101101
- Before you push, run `vp run check:changed`. It runs CI's fast checks for changed files: format, lint, knip, typecheck of affected packages and dependents, and tests beside changes. CI still runs the full test suites.
102102
- While you iterate, run `vp test run <files>`. For big files, add `-t "<name>"`.
103-
- Do not use `npx tsc`. Use `vp run typecheck`; it uses tsc-rs, which is 3x faster.
103+
- Use `vp run typecheck`, not `npx tsc`; it caches per package. Both run tsc-rs (`typescript` is the `@tsc-rs/typescript` drop-in).
104104
- Run `node -e` snippets from `apps/server` or the owning package. `effect` does not resolve from the repo root.
105105
- Test meaningful logic or observable behavior. Do not render components to static markup to assert props or attributes, or add tests that merely assert callback wiring or mirror the implementation.
106106
- **Do not run repo-wide checks.** No `vp check`, no `vp run -r test`, no `vp run -r typecheck` unless I ask. CI owns the full suite.
@@ -139,6 +139,7 @@ For authorized mobile verification, a missing or outdated native client is a bui
139139
## Pull requests
140140

141141
- Never make a PR unless the developer explicitly asks you to do so.
142+
- If `origin` is git.cafe, follow [GitCafe mirror](docs/operations/development.md#gitcafe-mirror-optional): use `cafe` for existing PRs, issues, comments and labels, but push and open PRs on GitHub, where CI runs.
142143
- Conventional commit titles, plain language: `fix(web): new threads no longer spike CPU`.
143144
- Body: the problem in a sentence or two, then how you fixed it. End with the model and harness that did the work.
144145
- UI changes need before/after images. Motion or timing needs a short video.

‎apps/desktop/package.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@t3tools/desktop",
3-
"version": "0.1.1",
3+
"version": "0.1.2",
44
"private": true,
55
"type": "module",
66
"main": "dist-electron/boot.cjs",

‎apps/desktop/src/app/DesktopObservability.ts‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -366,19 +366,19 @@ const resolveOtlpEndpoints = Effect.gen(function* () {
366366
otel,
367367
"traces",
368368
{ url: Option.getOrUndefined(environment.otlpTracesUrl), export: signalExport },
369-
persisted.otlpTracesUrl,
369+
{ bootstrapUrl: undefined, settingsUrl: persisted.otlpTracesUrl },
370370
),
371371
metrics: OtelEnvironment.resolveSignalEndpoint(
372372
otel,
373373
"metrics",
374374
{ url: Option.getOrUndefined(environment.otlpMetricsUrl), export: signalExport },
375-
persisted.otlpMetricsUrl,
375+
{ bootstrapUrl: undefined, settingsUrl: persisted.otlpMetricsUrl },
376376
),
377377
logs: OtelEnvironment.resolveSignalEndpoint(
378378
otel,
379379
"logs",
380380
{ url: Option.getOrUndefined(environment.otlpLogsUrl), export: signalExport },
381-
persisted.otlpLogsUrl,
381+
{ bootstrapUrl: undefined, settingsUrl: persisted.otlpLogsUrl },
382382
),
383383
warnings: otel.warnings,
384384
resourceAttributes: otel.resourceAttributes,

‎apps/desktop/src/updates/updateMachine.test.ts‎

Lines changed: 0 additions & 54 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@ import {
88
reduceDesktopUpdateStateOnDownloadFailure,
99
reduceDesktopUpdateStateOnInstallFailure,
1010
reduceDesktopUpdateStateOnNoUpdate,
11-
reduceDesktopUpdateStateOnUpdateAvailable,
1211
} from "./updateMachine.ts";
1312

1413
const runtimeInfo = {
@@ -50,30 +49,6 @@ describe("updateMachine", () => {
5049
expect(failed.message).toBeNull();
5150
});
5251

53-
it("keeps the installer when the feed still offers its version", () => {
54-
const releaseNotes = [{ version: "1.1.0", items: ["fix: queued update"], totalItems: 1 }];
55-
const state = reduceDesktopUpdateStateOnUpdateAvailable(
56-
{
57-
...createInitialDesktopUpdateState("1.0.0", runtimeInfo, "latest"),
58-
enabled: true,
59-
status: "downloaded",
60-
availableVersion: "1.1.0",
61-
downloadedVersion: "1.1.0",
62-
releaseNotes,
63-
omittedReleaseCount: 2,
64-
downloadPercent: 100,
65-
},
66-
"1.1.0",
67-
"2026-03-04T00:00:00.000Z",
68-
);
69-
70-
expect(state.status).toBe("downloaded");
71-
expect(state.downloadedVersion).toBe("1.1.0");
72-
expect(state.releaseNotes).toEqual(releaseNotes);
73-
expect(state.omittedReleaseCount).toBe(2);
74-
expect(state.downloadPercent).toBe(100);
75-
});
76-
7752
it("preserves available version on download failure for retry", () => {
7853
const state = reduceDesktopUpdateStateOnDownloadFailure(
7954
{
@@ -114,35 +89,6 @@ describe("updateMachine", () => {
11489
expect(failedInstall.canRetry).toBe(true);
11590
});
11691

117-
it("preserves a downloaded update when no update is available", () => {
118-
const releaseNotes = [{ version: "1.1.0", items: ["fix: queued update"], totalItems: 1 }];
119-
const state = reduceDesktopUpdateStateOnNoUpdate(
120-
{
121-
...createInitialDesktopUpdateState("1.0.0", runtimeInfo, "latest"),
122-
enabled: true,
123-
status: "error",
124-
availableVersion: "1.1.0",
125-
downloadedVersion: "1.1.0",
126-
releaseNotes,
127-
omittedReleaseCount: 2,
128-
message: "old failure",
129-
errorContext: "download",
130-
canRetry: true,
131-
},
132-
"2026-03-04T00:00:00.000Z",
133-
);
134-
135-
expect(state.status).toBe("downloaded");
136-
expect(state.availableVersion).toBe("1.1.0");
137-
expect(state.downloadedVersion).toBe("1.1.0");
138-
expect(state.releaseNotes).toBe(releaseNotes);
139-
expect(state.omittedReleaseCount).toBe(2);
140-
expect(state.downloadPercent).toBe(100);
141-
expect(state.message).toBeNull();
142-
expect(state.errorContext).toBeNull();
143-
expect(state.canRetry).toBe(true);
144-
});
145-
14692
it("clears stale available state when no update is available", () => {
14793
const state = reduceDesktopUpdateStateOnNoUpdate(
14894
{

‎apps/desktop/src/wsl/DesktopWslEnvironment.ts‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -463,14 +463,14 @@ cd ${shellQuote(linuxServerDir)} && node <<'NODE' >/dev/null 2>&1
463463
// The sentinel must be a package the CLI bundle leaves external. It used to be
464464
// "effect", back when the bundle externalized its runtime deps and the whole
465465
// node_modules tree was unpacked. The bundle now inlines its JS dependencies,
466-
// so "effect" no longer exists on disk and only the native packages do —
467-
// resolving node-pty is what actually validates the unpacked tree.
466+
// so "effect" no longer exists on disk and only the native packages do.
467+
// Resolving node-pty is what actually validates the unpacked tree.
468468
try { require.resolve("node-pty/package.json"); } catch (_e) { process.exit(3); }
469469
const fs = require("node:fs");
470470
const path = require("node:path");
471471
const pkgDir = path.dirname(require.resolve("node-pty/package.json"));
472472
// node-pty 1.x is N-API based, so a single Linux pty.node is ABI-stable across
473-
// Node versions — require() succeeding IS the real compatibility test. Look in
473+
// Node versions, so require() succeeding IS the real compatibility test. Look in
474474
// the same places node-pty's own loader does.
475475
const candidates = [
476476
path.join(pkgDir, "build", "Release", "pty.node"),
@@ -699,7 +699,7 @@ const ensureNodePtyImpl = Effect.fn("DesktopWslEnvironment.ensureNodePtyImpl")(f
699699
return {
700700
ok: false,
701701
reason:
702-
'WSL server dependencies could not be loaded (for example "node-pty"). The native packages the server needs are not unpacked where the WSL distro\'s Node can read them — this is a packaging problem with this build. Please report it.',
702+
'WSL server dependencies could not be loaded (for example "node-pty"). The native packages the server needs are not unpacked where the WSL distro\'s Node can read them. This is a packaging problem with this build. Please report it.',
703703
fatal: true,
704704
} as const;
705705
}

0 commit comments

Comments
 (0)