nodejs24 (v24.14.1) segfaults running @typespec/compiler; works on upstream Node 24

[sebader]

Describe the bug

The nodejs24 package shipped in Azure Linux 3.0 (v24.14.1) segfaults deterministically when running TypeSpec's compiler. The same version of TypeSpec running on official upstream Node 24.14.1 (node:24 / node:24-alpine Docker images) works fine. The distinguishing detail is that the Azure Linux build reports V8 as 13.6.233.17-node.44, while official upstream v24.14.1 reports 13.6.233.17-node.48 — i.e. this looks like a distro-specific Node patch.

This blocks internal Microsoft teams (mine and at least one neighboring team) from using mcr.microsoft.com/onebranch/azurelinux/build:3.0 as a TypeSpec-capable build image. We are currently working around it by pinning very old TypeSpec versions that happen not to trigger the V8 crash.

To Reproduce

docker run --rm mcr.microsoft.com/onebranch/azurelinux/build:3.0 bash -lc '
mkdir -p /tmp/mre && cd /tmp/mre
echo "{\"dependencies\":{\"@typespec/compiler\":\"1.11.0\"}}" > package.json
npm install --silent --ignore-scripts
echo "namespace Demo; model W { id: string; }" > main.tsp
./node_modules/.bin/tsp compile main.tsp --no-emit
'
# → "TypeSpec compiler v1.11.0" then Segmentation fault, exit 139

Reproduces 5/5 times. The same script against node:24 or node:24-alpine succeeds 5/5.

node -e "console.log(process.versions.v8)" on the Azure Linux 3.0 image prints 13.6.233.17-node.44; on official node:24 it prints 13.6.233.17-node.48.

Expected behavior

TypeSpec compiles the input file and exits 0, as it does on the corresponding upstream Node 24 build.

Additional context

• Tested on aarch64; would expect the same on x86_64.
• TypeSpec @typespec/compiler versions ≥ 1.2.0 trigger the crash; 1.1.0 does not. We have no reason to believe TypeSpec itself is at fault — the bug only manifests on the Azure Linux Node build.
• We can repro on demand if it helps narrow down which V8 / Node patch the Azure Linux package is missing relative to upstream node.48.

[sebader]

Update: this is the same root cause as the (closed) #16014, but the workaround proposed there (tdnf install nodejs24-full-i18n) does not work on linux/amd64 in the current image — the data subpackage ships the wrong ICU version:

$ docker run --rm --platform linux/amd64 mcr.microsoft.com/onebranch/azurelinux/build:3.0 bash -c '
    tdnf install -y nodejs24-full-i18n >/dev/null
    node -e "console.log(\"icu_ver_major:\", process.config.variables.icu_ver_major)"
    ls /usr/share/nodejs/icudata
    NODE_ICU_DATA=/usr/share/nodejs/icudata node -e "new Intl.Segmenter().segment(\"x\")"'

icu_ver_major: 78
icudt77l.dat
node: U_FILE_ACCESS_ERROR: Could not initialize ICU. Check the directory specified by NODE_ICU_DATA or --icu-data-dir contains icudt78l.dat and it's readable

So on amd64 we have a version mismatch:

	amd64
nodejs24 binary built against ICU	78
nodejs24-full-i18n data file	icudt77l.dat (ICU 77)

Note: the nodejs24.spec declares %global icu_major 77 throughout, so the spec and the data subpackage agree — but the produced amd64 binary diverges (process.config.variables.icu_ver_major: 78). On aarch64 the binary appears to be built against ICU 77, matching the data file, and nodejs24-full-i18n does fix the segfault there.

Workaround we are using on amd64: downgrade to the previous Azure Linux release nodejs24-24.13.0-3.azl3, which is internally consistent (binary + full-i18n both ICU 77) and runs the latest TypeSpec compiler correctly. Verified in the OneBranch build image:

tdnf install -y --allowerasing \
  nodejs24-24.13.0-3.azl3 \
  nodejs24-npm-24.13.0-3.azl3 \
  nodejs24-full-i18n-24.13.0-3.azl3

The 24.14.1 amd64 packages currently in the repos (both -1 and -2) are unusable for any tool that touches Intl.Segmenter, regardless of whether nodejs24-full-i18n is installed. Either the amd64 nodejs24-full-i18n needs to ship icudt78l.dat, or the nodejs24 binary needs to be rebuilt against ICU 77 to match the spec/data subpackage. Reopening #16014 (or treating this as a separate packaging bug) would be appreciated.