Skip to content

[Bug]: no build available for darwin-x64 platform for tags latest and nightly #12218

Closed as not planned
Closed as not planned
[Bug]: no build available for darwin-x64 platform for tags latest and nightly#12218
Labels
bugSomething is broken or behaving incorrectly.upstreamvia-triageFiled through npx t3 triagewontfixThis will not be worked on

Description

@omgmanu
omgmanu
opened on Sep 17, 2026

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

  1. be on darwin-x64 platform (ex: macbook with intel chip); double check platform and node version with node -p "process.platform+'-'+process.arch+' node '+process.version" (I have darwin-x64 node v24.18.0)
  2. try to run npx t3@nightly serve or npx t3@latest serve
  3. observe the error: t3: no T3 Code CLI build is available for this platform (darwin-x64). Supported platforms: darwin-arm64, linux-arm64, linux-x64, win32-arm64, win32-x64. If yours is listed, reinstall t3 so npm fetches its optional dependency.
  4. T3 Code does not start

Expected behavior

The T3 Code should install the tag's specific version and start the serve action. Ex: Starting T3 Code... Waiting for T3 to start... npm warn exec The following package was not found and will be installed: t3@0.0.4X

Actual behavior

T3 Code does not start for latest and nightly.

Impact

Blocks work completely

Version or commit

No response

Environment

No response

Logs or stack traces



Screenshots, recordings, or supporting files


No response


Workaround


using npx t3@0.0.40 serve the server starts.
Activity
  1. omgmanu
    added 
    bugSomething is broken or behaving incorrectly.
     
    needs-triageIssue needs maintainer review and initial categorization.
     on Sep 17, 2026
  2. omgmanu
    changed the title [-][Bug]: no build available for darwin-x64 platform[/-] [+][Bug]: no build available for darwin-x64 platform for tags `latest` and `nightly`[/+] on Sep 17, 2026
  3. juliusmarminge commented on Sep 17, 2026 
    @juliusmarminge
    juliusmarminge
    on Sep 17, 2026
    Member
    Triage
    

    Thanks for the clear repro — this is working as designed after the self-contained CLI cutover, not a missed latest/nightly publish.
    

    Since 0.0.42, npx t3 is only a launcher. It execs a Node single-executable from @t3code/t3-<platform>. Those archives are built for five targets: darwin-arm64, linux-arm64, linux-x64, win32-arm64, win32-x64. There is no darwin-x64 package (npm 404s @t3code/t3-darwin-x64), and v0.0.42 has no t3-*-darwin-x64 GitHub asset.
    

    Node’s SEA support is macOS arm64 only. An Intel SEA binary segfaults on start (Node SEA platform support, nodejs/node#62893). That is why PR #11605 omitted the archive and PR #11607 made npx t3 print the error you hit.
    

    npx t3@0.0.40 serve still works because 0.0.40 (2026-09-08) is the last stable that ran as a normal Node package, before SEA archives. That pin will not get current fixes.
    

    Supported options on an Intel Mac
    

      

    1. Desktop app (still shipped for x64): GitHub Releases → T3-Code-*-x64.dmg, or the Intel link on t3.codes/download.
      2. 

    2. Server from source (Intel Macs in the install docs):
      3. 

    

    git clone https://github.com/pingdotgg/t3code
cd t3code && vp i && vp run build:desktop
node apps/server/dist/bin.mjs
    

    We are not going to publish a darwin-x64 CLI while Node SEA is unsupported there. Closing this as a known upstream limitation (wontfix / upstream). The error text could mention Intel Macs and the desktop/source paths more directly; that would be a separate docs/UX change, not a new archive.
  4. juliusmarminge
    added 
    wontfixThis will not be worked on
     
    upstream
     
    via-triageFiled through npx t3 triage
     and removed 
    needs-triageIssue needs maintainer review and initial categorization.
     on Sep 17, 2026
  5. juliusmarminge
    closed this as not plannedon Sep 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Metadata
Assignees
No one assigned
    Labels
    bugSomething is broken or behaving incorrectly.upstreamvia-triageFiled through npx t3 triagewontfixThis will not be worked on
    Type
    No type
    Projects
    No projects
      Milestone
      No milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions