pingdotgg / pingdotgg/t3code

[Bug]: Can't install t3 via npm on remote debian 13 (VM)

Open
#11,823 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

accepted bug via-triage
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/server

Steps to reproduce
  • create a Debian VM (Linux 6.12.107+deb13-amd64)
  • install node 26 via nvm
  • run npx --loglevel verbose t3@latest connect
  • see the error
Expected behavior

it would install and show the sign in flow

Actual behavior

the t3 version install is stopped at the node-pty

(...)
npm info run msgpackr-extract@3.0.4 install node_modules/msgpackr-extract node-gyp-build-optional-packages
npm info run node-pty@1.1.0 install node_modules/node-pty node scripts/prebuild.js || node-gyp rebuild
npm info run msgpackr-extract@3.0.4 install { code: 0, signal: null }
npm info run node-pty@1.1.0 install { code: 1, signal: null }
npm verbose cwd /home/moda20
npm verbose os Linux 6.12.107+deb13-amd64
npm verbose node v26.8.2
npm verbose npm  v11.19.1
npm verbose exit 1
npm verbose code 1

This doesn't work for the latest preview or nightly as well (at least as of writing this) but they have a different issue :

t3: no T3 Code CLI build is available for this platform (linux-x64).
Supported platforms: darwin-arm64, linux-arm64, linux-x64, win32-arm64, win32-x64.
Impact

Blocks work completely

Version or commit

t3 latest (0.0.40)

Environment

Debina 13 VM amd64 x86

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing npx --loglevel verbose t3@latest connect on a Debian 13 amd64 VM with Node 26, focusing on the apps/server area and the node-pty install step in scripts/prebuild.js. Investigate the reported install failure and compare it with the preview/nightly platform-build error; done means the latest package installs and reaches the sign-in flow on Debian amd64.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian, linux, node.js, typescript
Domain
backend, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.