Adopt Node-native TypeScript for desktop and server

[juliusmarminge]

Makes dev work on windows

Summary

• Switch desktop and server entrypoints and scripts to Node-native TypeScript execution.
• Update local imports to include explicit .ts extensions and tighten type-only imports across the codebase.
• Adjust TypeScript configs and package scripts for the new module/runtime setup.
• Add and expand tests for release tooling and runtime helpers affected by the migration.

Testing

• Not run (PR content prepared from the committed changes).
• Existing Vitest coverage was updated alongside the TypeScript/runtime migration.
• New tests were added for scripts such as manifest merging, mock update server behavior, and release package version updates.

---

Note

Medium Risk
Medium risk because it changes runtime entrypoints/build artifacts (Bun→Node execution, .js→.cjs, NodeNext import rules) across desktop and server; misconfigured paths or module resolution could break dev/build/packaging, especially Electron preload/main loading and release tooling.

Overview
Migrates desktop + server execution/build away from Bun-centric assumptions toward Node-native TypeScript (NodeNext), including switching many local relative imports to explicit .ts extensions and tightening import type usage to satisfy verbatimModuleSyntax/erasableSyntaxOnly.

Desktop now builds CommonJS artifacts as .cjs (e.g. main.cjs, preload.cjs) and updates Electron launch/start/dev/smoke-test code and CI verification accordingly; macOS launcher behavior is adjusted to skip the renamed app bundle in dev to avoid helper resource lookup issues.

Server scripts are updated to run under Node (node --watch dev, build:bundle via tsdown), publishing prep resolves catalog: deps into concrete versions, and runtime/version reads switch to importing package.json as an object. Web tsconfig adds overrides to opt out of some NodeNext strictness.

^{Reviewed by Cursor Bugbot for commit dacc401. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Adopt Node-native TypeScript module resolution for desktop and server packages

• Switches tsconfig.base.json to NodeNext module/moduleResolution with rewriteRelativeImportExtensions, erasableSyntaxOnly, and verbatimModuleSyntax, requiring explicit .ts extensions on all relative imports across apps/desktop, apps/server, packages/shared, packages/contracts, and packages/client-runtime.
• Desktop and server dev/start scripts now use node instead of bun; desktop build output switches from .js to .cjs via tsdown.config.ts, and all launchers, smoke tests, and CI steps are updated to reference main.cjs and preload.cjs.
• Scripts (merge-update-manifests, update-release-package-versions, mock-update-server) are rewritten as Effect-based CLIs with import.meta.main guards so importing them no longer triggers execution.
• qrCode.ts is refactored from a TypeScript namespace to top-level exports with non-null assertions to satisfy erasableSyntaxOnly.
• Risk: any tooling or import that previously resolved extensionless .ts paths will break; the apps/web tsconfig explicitly opts out by setting module: Preserve and verbatimModuleSyntax: false.

^{Macroscope summarized dacc401.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: bd35bb6e-7e67-467d-9984-1dc6dea69b31

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/node-typescript-dev

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Test asserts wrong property name TCODE_HOME
  • Fixed typo on line 66 of dev-runner.test.ts: changed env.TCODE_HOME to env.T3CODE_HOME to match the production code's property name.

Or push these changes by commenting:

@cursor push c76b559076

Preview (c76b559076)

diff --git a/scripts/dev-runner.test.ts b/scripts/dev-runner.test.ts--- a/scripts/dev-runner.test.ts+++ b/scripts/dev-runner.test.ts@@ -63,7 +63,7 @@
devUrl: undefined,
});
- assert.equal(env.TCODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));+ assert.equal(env.T3CODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));
}),
);

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 91f2896. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved

Large but mechanical build infrastructure change adopting Node's native TypeScript support. The diff is dominated by import path updates (adding .ts extensions), output file extension changes (.js → .cjs), and bun → node script runner switches. The qrCode.ts namespace-to-class refactor is purely syntactic. Runtime impact is limited to consistent file path updates for Electron artifacts.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Makes dev work on windows

Summary

• Switch desktop and server entrypoints and scripts to Node-native TypeScript execution.
• Update local imports to include explicit .ts extensions and tighten type-only imports across the codebase.
• Adjust TypeScript configs and package scripts for the new module/runtime setup.
• Add and expand tests for release tooling and runtime helpers affected by the migration.

Testing

• Not run (PR content prepared from the committed changes).
• Existing Vitest coverage was updated alongside the TypeScript/runtime migration.
• New tests were added for scripts such as manifest merging, mock update server behavior, and release package version updates.

---

Note

Medium Risk
Medium risk because it changes runtime entrypoints/build artifacts (Bun→Node execution, .js→.cjs, NodeNext import rules) across desktop and server; misconfigured paths or module resolution could break dev/build/packaging, especially Electron preload/main loading and release tooling.

Overview
Migrates desktop + server execution/build away from Bun-centric assumptions toward Node-native TypeScript (NodeNext), including switching many local relative imports to explicit .ts extensions and tightening import type usage to satisfy verbatimModuleSyntax/erasableSyntaxOnly.

Desktop now builds CommonJS artifacts as .cjs (e.g. main.cjs, preload.cjs) and updates Electron launch/start/dev/smoke-test code and CI verification accordingly; macOS launcher behavior is adjusted to skip the renamed app bundle in dev to avoid helper resource lookup issues.

Server scripts are updated to run under Node (node --watch dev, build:bundle via tsdown), publishing prep resolves catalog: deps into concrete versions, and runtime/version reads switch to importing package.json as an object. Web tsconfig adds overrides to opt out of some NodeNext strictness.

^{Reviewed by Cursor Bugbot for commit dacc401. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Adopt Node-native TypeScript module resolution for desktop and server packages

• Switches tsconfig.base.json to NodeNext module/moduleResolution with rewriteRelativeImportExtensions, erasableSyntaxOnly, and verbatimModuleSyntax, requiring explicit .ts extensions on all relative imports across apps/desktop, apps/server, packages/shared, packages/contracts, and packages/client-runtime.
• Desktop and server dev/start scripts now use node instead of bun; desktop build output switches from .js to .cjs via tsdown.config.ts, and all launchers, smoke tests, and CI steps are updated to reference main.cjs and preload.cjs.
• Scripts (merge-update-manifests, update-release-package-versions, mock-update-server) are rewritten as Effect-based CLIs with import.meta.main guards so importing them no longer triggers execution.
• qrCode.ts is refactored from a TypeScript namespace to top-level exports with non-null assertions to satisfy erasableSyntaxOnly.
• Risk: any tooling or import that previously resolved extensionless .ts paths will break; the apps/web tsconfig explicitly opts out by setting module: Preserve and verbatimModuleSyntax: false.

^{Macroscope summarized dacc401.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: bd35bb6e-7e67-467d-9984-1dc6dea69b31

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/node-typescript-dev

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Test asserts wrong property name TCODE_HOME
  • Fixed typo on line 66 of dev-runner.test.ts: changed env.TCODE_HOME to env.T3CODE_HOME to match the production code's property name.

Or push these changes by commenting:

@cursor push c76b559076

Preview (c76b559076)

diff --git a/scripts/dev-runner.test.ts b/scripts/dev-runner.test.ts--- a/scripts/dev-runner.test.ts+++ b/scripts/dev-runner.test.ts@@ -63,7 +63,7 @@
devUrl: undefined,
});
- assert.equal(env.TCODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));+ assert.equal(env.T3CODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));
}),
);

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 91f2896. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved

Large but mechanical build infrastructure change adopting Node's native TypeScript support. The diff is dominated by import path updates (adding .ts extensions), output file extension changes (.js → .cjs), and bun → node script runner switches. The qrCode.ts namespace-to-class refactor is purely syntactic. Runtime impact is limited to consistent file path updates for Electron artifacts.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Makes dev work on windows

Summary

• Switch desktop and server entrypoints and scripts to Node-native TypeScript execution.
• Update local imports to include explicit .ts extensions and tighten type-only imports across the codebase.
• Adjust TypeScript configs and package scripts for the new module/runtime setup.
• Add and expand tests for release tooling and runtime helpers affected by the migration.

Testing

• Not run (PR content prepared from the committed changes).
• Existing Vitest coverage was updated alongside the TypeScript/runtime migration.
• New tests were added for scripts such as manifest merging, mock update server behavior, and release package version updates.

---

Note

Medium Risk
Medium risk because it changes runtime entrypoints/build artifacts (Bun→Node execution, .js→.cjs, NodeNext import rules) across desktop and server; misconfigured paths or module resolution could break dev/build/packaging, especially Electron preload/main loading and release tooling.

Overview
Migrates desktop + server execution/build away from Bun-centric assumptions toward Node-native TypeScript (NodeNext), including switching many local relative imports to explicit .ts extensions and tightening import type usage to satisfy verbatimModuleSyntax/erasableSyntaxOnly.

Desktop now builds CommonJS artifacts as .cjs (e.g. main.cjs, preload.cjs) and updates Electron launch/start/dev/smoke-test code and CI verification accordingly; macOS launcher behavior is adjusted to skip the renamed app bundle in dev to avoid helper resource lookup issues.

Server scripts are updated to run under Node (node --watch dev, build:bundle via tsdown), publishing prep resolves catalog: deps into concrete versions, and runtime/version reads switch to importing package.json as an object. Web tsconfig adds overrides to opt out of some NodeNext strictness.

^{Reviewed by Cursor Bugbot for commit dacc401. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Adopt Node-native TypeScript module resolution for desktop and server packages

• Switches tsconfig.base.json to NodeNext module/moduleResolution with rewriteRelativeImportExtensions, erasableSyntaxOnly, and verbatimModuleSyntax, requiring explicit .ts extensions on all relative imports across apps/desktop, apps/server, packages/shared, packages/contracts, and packages/client-runtime.
• Desktop and server dev/start scripts now use node instead of bun; desktop build output switches from .js to .cjs via tsdown.config.ts, and all launchers, smoke tests, and CI steps are updated to reference main.cjs and preload.cjs.
• Scripts (merge-update-manifests, update-release-package-versions, mock-update-server) are rewritten as Effect-based CLIs with import.meta.main guards so importing them no longer triggers execution.
• qrCode.ts is refactored from a TypeScript namespace to top-level exports with non-null assertions to satisfy erasableSyntaxOnly.
• Risk: any tooling or import that previously resolved extensionless .ts paths will break; the apps/web tsconfig explicitly opts out by setting module: Preserve and verbatimModuleSyntax: false.

^{Macroscope summarized dacc401.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: bd35bb6e-7e67-467d-9984-1dc6dea69b31

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/node-typescript-dev

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Test asserts wrong property name TCODE_HOME
  • Fixed typo on line 66 of dev-runner.test.ts: changed env.TCODE_HOME to env.T3CODE_HOME to match the production code's property name.

Or push these changes by commenting:

@cursor push c76b559076

Preview (c76b559076)

diff --git a/scripts/dev-runner.test.ts b/scripts/dev-runner.test.ts--- a/scripts/dev-runner.test.ts+++ b/scripts/dev-runner.test.ts@@ -63,7 +63,7 @@
devUrl: undefined,
});
- assert.equal(env.TCODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));+ assert.equal(env.T3CODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));
}),
);

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 91f2896. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved

Large but mechanical build infrastructure change adopting Node's native TypeScript support. The diff is dominated by import path updates (adding .ts extensions), output file extension changes (.js → .cjs), and bun → node script runner switches. The qrCode.ts namespace-to-class refactor is purely syntactic. Runtime impact is limited to consistent file path updates for Electron artifacts.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Makes dev work on windows

Summary

• Switch desktop and server entrypoints and scripts to Node-native TypeScript execution.
• Update local imports to include explicit .ts extensions and tighten type-only imports across the codebase.
• Adjust TypeScript configs and package scripts for the new module/runtime setup.
• Add and expand tests for release tooling and runtime helpers affected by the migration.

Testing

• Not run (PR content prepared from the committed changes).
• Existing Vitest coverage was updated alongside the TypeScript/runtime migration.
• New tests were added for scripts such as manifest merging, mock update server behavior, and release package version updates.

---

Note

Medium Risk
Medium risk because it changes runtime entrypoints/build artifacts (Bun→Node execution, .js→.cjs, NodeNext import rules) across desktop and server; misconfigured paths or module resolution could break dev/build/packaging, especially Electron preload/main loading and release tooling.

Overview
Migrates desktop + server execution/build away from Bun-centric assumptions toward Node-native TypeScript (NodeNext), including switching many local relative imports to explicit .ts extensions and tightening import type usage to satisfy verbatimModuleSyntax/erasableSyntaxOnly.

Desktop now builds CommonJS artifacts as .cjs (e.g. main.cjs, preload.cjs) and updates Electron launch/start/dev/smoke-test code and CI verification accordingly; macOS launcher behavior is adjusted to skip the renamed app bundle in dev to avoid helper resource lookup issues.

Server scripts are updated to run under Node (node --watch dev, build:bundle via tsdown), publishing prep resolves catalog: deps into concrete versions, and runtime/version reads switch to importing package.json as an object. Web tsconfig adds overrides to opt out of some NodeNext strictness.

^{Reviewed by Cursor Bugbot for commit dacc401. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Adopt Node-native TypeScript module resolution for desktop and server packages

• Switches tsconfig.base.json to NodeNext module/moduleResolution with rewriteRelativeImportExtensions, erasableSyntaxOnly, and verbatimModuleSyntax, requiring explicit .ts extensions on all relative imports across apps/desktop, apps/server, packages/shared, packages/contracts, and packages/client-runtime.
• Desktop and server dev/start scripts now use node instead of bun; desktop build output switches from .js to .cjs via tsdown.config.ts, and all launchers, smoke tests, and CI steps are updated to reference main.cjs and preload.cjs.
• Scripts (merge-update-manifests, update-release-package-versions, mock-update-server) are rewritten as Effect-based CLIs with import.meta.main guards so importing them no longer triggers execution.
• qrCode.ts is refactored from a TypeScript namespace to top-level exports with non-null assertions to satisfy erasableSyntaxOnly.
• Risk: any tooling or import that previously resolved extensionless .ts paths will break; the apps/web tsconfig explicitly opts out by setting module: Preserve and verbatimModuleSyntax: false.

^{Macroscope summarized dacc401.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: bd35bb6e-7e67-467d-9984-1dc6dea69b31

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/node-typescript-dev

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Test asserts wrong property name TCODE_HOME
  • Fixed typo on line 66 of dev-runner.test.ts: changed env.TCODE_HOME to env.T3CODE_HOME to match the production code's property name.

Or push these changes by commenting:

@cursor push c76b559076

Preview (c76b559076)

diff --git a/scripts/dev-runner.test.ts b/scripts/dev-runner.test.ts--- a/scripts/dev-runner.test.ts+++ b/scripts/dev-runner.test.ts@@ -63,7 +63,7 @@
devUrl: undefined,
});
- assert.equal(env.TCODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));+ assert.equal(env.T3CODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));
}),
);

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 91f2896. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved

Large but mechanical build infrastructure change adopting Node's native TypeScript support. The diff is dominated by import path updates (adding .ts extensions), output file extension changes (.js → .cjs), and bun → node script runner switches. The qrCode.ts namespace-to-class refactor is purely syntactic. Runtime impact is limited to consistent file path updates for Electron artifacts.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Makes dev work on windows

Summary

• Switch desktop and server entrypoints and scripts to Node-native TypeScript execution.
• Update local imports to include explicit .ts extensions and tighten type-only imports across the codebase.
• Adjust TypeScript configs and package scripts for the new module/runtime setup.
• Add and expand tests for release tooling and runtime helpers affected by the migration.

Testing

• Not run (PR content prepared from the committed changes).
• Existing Vitest coverage was updated alongside the TypeScript/runtime migration.
• New tests were added for scripts such as manifest merging, mock update server behavior, and release package version updates.

---

Note

Medium Risk
Medium risk because it changes runtime entrypoints/build artifacts (Bun→Node execution, .js→.cjs, NodeNext import rules) across desktop and server; misconfigured paths or module resolution could break dev/build/packaging, especially Electron preload/main loading and release tooling.

Overview
Migrates desktop + server execution/build away from Bun-centric assumptions toward Node-native TypeScript (NodeNext), including switching many local relative imports to explicit .ts extensions and tightening import type usage to satisfy verbatimModuleSyntax/erasableSyntaxOnly.

Desktop now builds CommonJS artifacts as .cjs (e.g. main.cjs, preload.cjs) and updates Electron launch/start/dev/smoke-test code and CI verification accordingly; macOS launcher behavior is adjusted to skip the renamed app bundle in dev to avoid helper resource lookup issues.

Server scripts are updated to run under Node (node --watch dev, build:bundle via tsdown), publishing prep resolves catalog: deps into concrete versions, and runtime/version reads switch to importing package.json as an object. Web tsconfig adds overrides to opt out of some NodeNext strictness.

^{Reviewed by Cursor Bugbot for commit dacc401. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Adopt Node-native TypeScript module resolution for desktop and server packages

• Switches tsconfig.base.json to NodeNext module/moduleResolution with rewriteRelativeImportExtensions, erasableSyntaxOnly, and verbatimModuleSyntax, requiring explicit .ts extensions on all relative imports across apps/desktop, apps/server, packages/shared, packages/contracts, and packages/client-runtime.
• Desktop and server dev/start scripts now use node instead of bun; desktop build output switches from .js to .cjs via tsdown.config.ts, and all launchers, smoke tests, and CI steps are updated to reference main.cjs and preload.cjs.
• Scripts (merge-update-manifests, update-release-package-versions, mock-update-server) are rewritten as Effect-based CLIs with import.meta.main guards so importing them no longer triggers execution.
• qrCode.ts is refactored from a TypeScript namespace to top-level exports with non-null assertions to satisfy erasableSyntaxOnly.
• Risk: any tooling or import that previously resolved extensionless .ts paths will break; the apps/web tsconfig explicitly opts out by setting module: Preserve and verbatimModuleSyntax: false.

^{Macroscope summarized dacc401.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: bd35bb6e-7e67-467d-9984-1dc6dea69b31

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/node-typescript-dev

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Test asserts wrong property name TCODE_HOME
  • Fixed typo on line 66 of dev-runner.test.ts: changed env.TCODE_HOME to env.T3CODE_HOME to match the production code's property name.

Or push these changes by commenting:

@cursor push c76b559076

Preview (c76b559076)

diff --git a/scripts/dev-runner.test.ts b/scripts/dev-runner.test.ts--- a/scripts/dev-runner.test.ts+++ b/scripts/dev-runner.test.ts@@ -63,7 +63,7 @@
devUrl: undefined,
});
- assert.equal(env.TCODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));+ assert.equal(env.T3CODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));
}),
);

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 91f2896. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved

Large but mechanical build infrastructure change adopting Node's native TypeScript support. The diff is dominated by import path updates (adding .ts extensions), output file extension changes (.js → .cjs), and bun → node script runner switches. The qrCode.ts namespace-to-class refactor is purely syntactic. Runtime impact is limited to consistent file path updates for Electron artifacts.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Makes dev work on windows

Summary

• Switch desktop and server entrypoints and scripts to Node-native TypeScript execution.
• Update local imports to include explicit .ts extensions and tighten type-only imports across the codebase.
• Adjust TypeScript configs and package scripts for the new module/runtime setup.
• Add and expand tests for release tooling and runtime helpers affected by the migration.

Testing

• Not run (PR content prepared from the committed changes).
• Existing Vitest coverage was updated alongside the TypeScript/runtime migration.
• New tests were added for scripts such as manifest merging, mock update server behavior, and release package version updates.

---

Note

Medium Risk
Medium risk because it changes runtime entrypoints/build artifacts (Bun→Node execution, .js→.cjs, NodeNext import rules) across desktop and server; misconfigured paths or module resolution could break dev/build/packaging, especially Electron preload/main loading and release tooling.

Overview
Migrates desktop + server execution/build away from Bun-centric assumptions toward Node-native TypeScript (NodeNext), including switching many local relative imports to explicit .ts extensions and tightening import type usage to satisfy verbatimModuleSyntax/erasableSyntaxOnly.

Desktop now builds CommonJS artifacts as .cjs (e.g. main.cjs, preload.cjs) and updates Electron launch/start/dev/smoke-test code and CI verification accordingly; macOS launcher behavior is adjusted to skip the renamed app bundle in dev to avoid helper resource lookup issues.

Server scripts are updated to run under Node (node --watch dev, build:bundle via tsdown), publishing prep resolves catalog: deps into concrete versions, and runtime/version reads switch to importing package.json as an object. Web tsconfig adds overrides to opt out of some NodeNext strictness.

^{Reviewed by Cursor Bugbot for commit dacc401. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Adopt Node-native TypeScript module resolution for desktop and server packages

• Switches tsconfig.base.json to NodeNext module/moduleResolution with rewriteRelativeImportExtensions, erasableSyntaxOnly, and verbatimModuleSyntax, requiring explicit .ts extensions on all relative imports across apps/desktop, apps/server, packages/shared, packages/contracts, and packages/client-runtime.
• Desktop and server dev/start scripts now use node instead of bun; desktop build output switches from .js to .cjs via tsdown.config.ts, and all launchers, smoke tests, and CI steps are updated to reference main.cjs and preload.cjs.
• Scripts (merge-update-manifests, update-release-package-versions, mock-update-server) are rewritten as Effect-based CLIs with import.meta.main guards so importing them no longer triggers execution.
• qrCode.ts is refactored from a TypeScript namespace to top-level exports with non-null assertions to satisfy erasableSyntaxOnly.
• Risk: any tooling or import that previously resolved extensionless .ts paths will break; the apps/web tsconfig explicitly opts out by setting module: Preserve and verbatimModuleSyntax: false.

^{Macroscope summarized dacc401.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: bd35bb6e-7e67-467d-9984-1dc6dea69b31

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/node-typescript-dev

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Test asserts wrong property name TCODE_HOME
  • Fixed typo on line 66 of dev-runner.test.ts: changed env.TCODE_HOME to env.T3CODE_HOME to match the production code's property name.

Or push these changes by commenting:

@cursor push c76b559076

Preview (c76b559076)

diff --git a/scripts/dev-runner.test.ts b/scripts/dev-runner.test.ts--- a/scripts/dev-runner.test.ts+++ b/scripts/dev-runner.test.ts@@ -63,7 +63,7 @@
devUrl: undefined,
});
- assert.equal(env.TCODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));+ assert.equal(env.T3CODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));
}),
);

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 91f2896. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved

Large but mechanical build infrastructure change adopting Node's native TypeScript support. The diff is dominated by import path updates (adding .ts extensions), output file extension changes (.js → .cjs), and bun → node script runner switches. The qrCode.ts namespace-to-class refactor is purely syntactic. Runtime impact is limited to consistent file path updates for Electron artifacts.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Makes dev work on windows

Summary

• Switch desktop and server entrypoints and scripts to Node-native TypeScript execution.
• Update local imports to include explicit .ts extensions and tighten type-only imports across the codebase.
• Adjust TypeScript configs and package scripts for the new module/runtime setup.
• Add and expand tests for release tooling and runtime helpers affected by the migration.

Testing

• Not run (PR content prepared from the committed changes).
• Existing Vitest coverage was updated alongside the TypeScript/runtime migration.
• New tests were added for scripts such as manifest merging, mock update server behavior, and release package version updates.

---

Note

Medium Risk
Medium risk because it changes runtime entrypoints/build artifacts (Bun→Node execution, .js→.cjs, NodeNext import rules) across desktop and server; misconfigured paths or module resolution could break dev/build/packaging, especially Electron preload/main loading and release tooling.

Overview
Migrates desktop + server execution/build away from Bun-centric assumptions toward Node-native TypeScript (NodeNext), including switching many local relative imports to explicit .ts extensions and tightening import type usage to satisfy verbatimModuleSyntax/erasableSyntaxOnly.

Desktop now builds CommonJS artifacts as .cjs (e.g. main.cjs, preload.cjs) and updates Electron launch/start/dev/smoke-test code and CI verification accordingly; macOS launcher behavior is adjusted to skip the renamed app bundle in dev to avoid helper resource lookup issues.

Server scripts are updated to run under Node (node --watch dev, build:bundle via tsdown), publishing prep resolves catalog: deps into concrete versions, and runtime/version reads switch to importing package.json as an object. Web tsconfig adds overrides to opt out of some NodeNext strictness.

^{Reviewed by Cursor Bugbot for commit dacc401. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Adopt Node-native TypeScript module resolution for desktop and server packages

• Switches tsconfig.base.json to NodeNext module/moduleResolution with rewriteRelativeImportExtensions, erasableSyntaxOnly, and verbatimModuleSyntax, requiring explicit .ts extensions on all relative imports across apps/desktop, apps/server, packages/shared, packages/contracts, and packages/client-runtime.
• Desktop and server dev/start scripts now use node instead of bun; desktop build output switches from .js to .cjs via tsdown.config.ts, and all launchers, smoke tests, and CI steps are updated to reference main.cjs and preload.cjs.
• Scripts (merge-update-manifests, update-release-package-versions, mock-update-server) are rewritten as Effect-based CLIs with import.meta.main guards so importing them no longer triggers execution.
• qrCode.ts is refactored from a TypeScript namespace to top-level exports with non-null assertions to satisfy erasableSyntaxOnly.
• Risk: any tooling or import that previously resolved extensionless .ts paths will break; the apps/web tsconfig explicitly opts out by setting module: Preserve and verbatimModuleSyntax: false.

^{Macroscope summarized dacc401.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: bd35bb6e-7e67-467d-9984-1dc6dea69b31

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/node-typescript-dev

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Test asserts wrong property name TCODE_HOME
  • Fixed typo on line 66 of dev-runner.test.ts: changed env.TCODE_HOME to env.T3CODE_HOME to match the production code's property name.

Or push these changes by commenting:

@cursor push c76b559076

Preview (c76b559076)

diff --git a/scripts/dev-runner.test.ts b/scripts/dev-runner.test.ts--- a/scripts/dev-runner.test.ts+++ b/scripts/dev-runner.test.ts@@ -63,7 +63,7 @@
devUrl: undefined,
});
- assert.equal(env.TCODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));+ assert.equal(env.T3CODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));
}),
);

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 91f2896. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved

Large but mechanical build infrastructure change adopting Node's native TypeScript support. The diff is dominated by import path updates (adding .ts extensions), output file extension changes (.js → .cjs), and bun → node script runner switches. The qrCode.ts namespace-to-class refactor is purely syntactic. Runtime impact is limited to consistent file path updates for Electron artifacts.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

Makes dev work on windows

Summary

• Switch desktop and server entrypoints and scripts to Node-native TypeScript execution.
• Update local imports to include explicit .ts extensions and tighten type-only imports across the codebase.
• Adjust TypeScript configs and package scripts for the new module/runtime setup.
• Add and expand tests for release tooling and runtime helpers affected by the migration.

Testing

• Not run (PR content prepared from the committed changes).
• Existing Vitest coverage was updated alongside the TypeScript/runtime migration.
• New tests were added for scripts such as manifest merging, mock update server behavior, and release package version updates.

---

Note

Medium Risk
Medium risk because it changes runtime entrypoints/build artifacts (Bun→Node execution, .js→.cjs, NodeNext import rules) across desktop and server; misconfigured paths or module resolution could break dev/build/packaging, especially Electron preload/main loading and release tooling.

Overview
Migrates desktop + server execution/build away from Bun-centric assumptions toward Node-native TypeScript (NodeNext), including switching many local relative imports to explicit .ts extensions and tightening import type usage to satisfy verbatimModuleSyntax/erasableSyntaxOnly.

Desktop now builds CommonJS artifacts as .cjs (e.g. main.cjs, preload.cjs) and updates Electron launch/start/dev/smoke-test code and CI verification accordingly; macOS launcher behavior is adjusted to skip the renamed app bundle in dev to avoid helper resource lookup issues.

Server scripts are updated to run under Node (node --watch dev, build:bundle via tsdown), publishing prep resolves catalog: deps into concrete versions, and runtime/version reads switch to importing package.json as an object. Web tsconfig adds overrides to opt out of some NodeNext strictness.

^{Reviewed by Cursor Bugbot for commit dacc401. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Adopt Node-native TypeScript module resolution for desktop and server packages

• Switches tsconfig.base.json to NodeNext module/moduleResolution with rewriteRelativeImportExtensions, erasableSyntaxOnly, and verbatimModuleSyntax, requiring explicit .ts extensions on all relative imports across apps/desktop, apps/server, packages/shared, packages/contracts, and packages/client-runtime.
• Desktop and server dev/start scripts now use node instead of bun; desktop build output switches from .js to .cjs via tsdown.config.ts, and all launchers, smoke tests, and CI steps are updated to reference main.cjs and preload.cjs.
• Scripts (merge-update-manifests, update-release-package-versions, mock-update-server) are rewritten as Effect-based CLIs with import.meta.main guards so importing them no longer triggers execution.
• qrCode.ts is refactored from a TypeScript namespace to top-level exports with non-null assertions to satisfy erasableSyntaxOnly.
• Risk: any tooling or import that previously resolved extensionless .ts paths will break; the apps/web tsconfig explicitly opts out by setting module: Preserve and verbatimModuleSyntax: false.

^{Macroscope summarized dacc401.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: bd35bb6e-7e67-467d-9984-1dc6dea69b31

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/node-typescript-dev

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Test asserts wrong property name TCODE_HOME
  • Fixed typo on line 66 of dev-runner.test.ts: changed env.TCODE_HOME to env.T3CODE_HOME to match the production code's property name.

Or push these changes by commenting:

@cursor push c76b559076

Preview (c76b559076)

diff --git a/scripts/dev-runner.test.ts b/scripts/dev-runner.test.ts--- a/scripts/dev-runner.test.ts+++ b/scripts/dev-runner.test.ts@@ -63,7 +63,7 @@
devUrl: undefined,
});
- assert.equal(env.TCODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));+ assert.equal(env.T3CODE_HOME, path.resolve(NodeOS.homedir(), ".t3"));
}),
);

_{You can send follow-ups to the cloud agent here.}

^{Reviewed by Cursor Bugbot for commit 91f2896. Configure here.}

[macroscopeapp]

Approvability

Verdict: Approved

Large but mechanical build infrastructure change adopting Node's native TypeScript support. The diff is dominated by import path updates (adding .ts extensions), output file extension changes (.js → .cjs), and bun → node script runner switches. The qrCode.ts namespace-to-class refactor is purely syntactic. Runtime impact is limited to consistent file path updates for Electron artifacts.

^{You can customize Macroscope's approvability policy. Learn more.}