Publish prebuilt @scriptc/libnode-* packs with the native installer

Aperta
  • Qualcosa non va?
#2,915 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@ctate ci sta già lavorando.

Dal 5/11/2026.

  • #3006 di @ctate — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
nodejs, typescript
Ambito
build-system, release

Direzione di ricerca

Start with packages/cli/scripts/install-native.mjs (nativeCliPackage() is the naming template) and packages/libnode-common/build-pack.mjs, then check the private flag and publishConfig in the libnode platform package.json files. Decide how the installer resolves @scriptc/libnode-<host> and wires the optional dependency, and how the SC8005 hint changes. Done means a published install finds a libnode pack without a self-build. Release policy and optional-dependency wiring need maintainer input before coding.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

Node islands (@scriptc/node) need a prebuilt libnode pack. The repo already has platform packages (@scriptc/libnode-linux-x64-gnu, darwin-arm64, darwin-x64, linux-arm64-gnu, plus libnode-common) at version 0.4.7, with publishConfig.access: public, but they are "private": true and are not published. Downstream users must self-build (packages/libnode-common/build-pack.mjs, SCRIPTC_LIBNODE / --libnode). That is the whole cost of Tier-3 islands for T3 Code.

Expected

Publishing @scriptc/libnode-<platform> with the same installer pattern as packages/cli/scripts/install-native.mjs:

  1. Flip private off for the libnode platform packages on release (they already list files, os/cpu/libc, and prepack verify).
  2. Extend the native installer (or a sibling install-libnode.mjs required from the Node-island link path) to require.resolve("@scriptc/libnode-<host>/package.json") at the CLI version, then record that directory as the libnode pack (today's SCRIPTC_LIBNODE layout: libnode.so.* / libnode.dylib, libscr_node_bridge.so, manifest.json).
  3. If the optional dependency is missing, keep today's SC8005 with a hint that names pnpm install of the platform package, not only a self-build.
  4. Optional dependency wiring on scriptc / @scriptc/cli-<host> so npm i -g scriptc fetches libnode for that host the same way it fetches the native CLI bits.

nativeCliPackage() in install-native.mjs is the naming template. A libnodePackage(platform, arch, libc) mapping to @scriptc/libnode-linux-x64-gnu (etc.) is the same function with a different prefix.

Actual (0.4.7)

SC8005: no usable libnode pack. Hint points at SCRIPTC_LIBNODE and packages/libnode-common/build-pack.mjs. CI provides a pack via .github/actions/libnode; published installs do not.

Evidence

Plan E9.

Lingua principale
TypeScript
Stelle
6.4k
Fork
204
Merge medio
7h 35m
PR unite (30g)
873

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di vercel-labs/scriptc

Tutte le issue di vercel-labs/scriptc

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.