Summary
Windows Nightly 0.0.29-nightly.20260719.849 crashes on launch with a main-process ERR_MODULE_NOT_FOUND for effect/Context, imported from @effect/platform-node's NodeHttpClient.js.
This looks like a packaging regression: effect (and related deps) are listed in the asar index as unpacked files, but are not present under resources/app.asar.unpacked/node_modules/.
Area
Build, CI, or release tooling / Desktop packaging
Steps to reproduce
- Install T3 Code Nightly 0.0.29-nightly.20260719.849 on Windows x64 (
T3-Code-0.0.29-nightly.20260719.849-x64.exe)
- Launch T3 Code (Nightly)
Expected behavior
App launches normally.
Actual behavior
Uncaught exception dialog:
A JavaScript error occurred in the main process
Uncaught Exception:
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '...app.asar\node_modul...\Context'
imported from '...app.asar\...\NodeHttpClient.js'
Stack points at Node ESM resolution (finalizeResolution / moduleResolve).
Investigation notes
On a machine with 849 installed:
- Import path in packaged code:
import * as Context from "effect/Context" from @effect/platform-node/dist/NodeHttpClient.js
@effect/platform-node is present under app.asar.unpacked/node_modules/@effect/platform-nodeeffect is missing from app.asar.unpacked/node_modules/effect- Extracting
node_modules\effect\package.json / dist\Context.js via @electron/asar fails with ENOENT under app.asar.unpacked\... (files marked unpacked but not on disk)
- Related deps also missing from unpacked in that build:
undici, mime (peer/runtime deps of @effect/platform-node)
This is distinct from (but in the same family as) #3789 / #3790 (pnpm 11 deduped deps dropped from asar). Here the failure mode is specifically unpacked index entries with missing unpacked payloads.
Workaround
Rolling back to a prior Nightly works. Confirmed working:
0.0.29-nightly.20260712.791 (local updater cache installer; effect/dist/Context.js present under app.asar.unpacked)
Environment
- OS: Windows 10/11 (win32 10.0.26200), x64
- App: T3 Code (Nightly)
0.0.29-nightly.20260719.849
- Install path:
%LocalAppData%\Programs\t3code
Impact
Blocks Nightly launch completely on Windows for this build.
Happy to provide more asar listings / installer hashes if useful.
Summary
Windows Nightly
0.0.29-nightly.20260719.849crashes on launch with a main-processERR_MODULE_NOT_FOUNDforeffect/Context, imported from@effect/platform-node'sNodeHttpClient.js.This looks like a packaging regression:
effect(and related deps) are listed in the asar index as unpacked files, but are not present underresources/app.asar.unpacked/node_modules/.Area
Build, CI, or release tooling / Desktop packaging
Steps to reproduce
T3-Code-0.0.29-nightly.20260719.849-x64.exe)Expected behavior
App launches normally.
Actual behavior
Uncaught exception dialog:
Stack points at Node ESM resolution (
finalizeResolution/moduleResolve).Investigation notes
On a machine with
849installed:import * as Context from "effect/Context"from@effect/platform-node/dist/NodeHttpClient.js@effect/platform-nodeis present underapp.asar.unpacked/node_modules/@effect/platform-nodeeffectis missing fromapp.asar.unpacked/node_modules/effectnode_modules\effect\package.json/dist\Context.jsvia@electron/asarfails withENOENTunderapp.asar.unpacked\...(files marked unpacked but not on disk)undici,mime(peer/runtime deps of@effect/platform-node)This is distinct from (but in the same family as) #3789 / #3790 (pnpm 11 deduped deps dropped from asar). Here the failure mode is specifically unpacked index entries with missing unpacked payloads.
Workaround
Rolling back to a prior Nightly works. Confirmed working:
0.0.29-nightly.20260712.791(local updater cache installer;effect/dist/Context.jspresent underapp.asar.unpacked)Environment
0.0.29-nightly.20260719.849%LocalAppData%\Programs\t3codeImpact
Blocks Nightly launch completely on Windows for this build.
Happy to provide more asar listings / installer hashes if useful.