[Bug]: T3 Code 0.0.40 desktop UI: "T3 Code could not load"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/desktop
Steps to reproduce
- Download the T3 Code 0.0.40 Linux AppImage.
- Make it executable.
- Launch it normally:
./T3-Code.AppImage - The Electron window opens but displays “T3 Code could not load.”
For more detailed logging: ./T3-Code.AppImage --enable-logging=stderr --v=1
Expected behavior
The desktop UI should load normally after the backend starts.
Actual behavior
The renderer fails while loading the bundled UI:
T3 Code failed to start. SyntaxError: The requested module './ConnectionStatusDot-DxBlMuxG.js' does not provide an export named 't'
source: t3code://app/assets/index-69CxTXc4.js (2)
Impact
Blocks work completely
Version or commit
No response
Environment
T3 Code: 0.0.40, Package: Linux AppImage, Desktop environment: Cinnamon Linux, distribution: Linux Mint
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in apps/desktop and reproduce the failure with the Linux AppImage using the provided launch command and logging flags. Trace the bundled renderer references from assets/index-69CxTXc4.js to ConnectionStatusDot-DxBlMuxG.js and investigate the missing export. Done means the packaged T3 Code 0.0.40 desktop UI loads normally after the backend starts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, typescript
- Domain
- build-system, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100