Cross-compilation from macOS to Linux on arm64 broken on >=22 #181

Activity

1. robertsLando commented on Oct 16, 2025

   

   robertsLando

   on Oct 16, 2025

   Member

   More actions

   Please show me package.json content and also share pkg command output with --debug flag. Then run the result package with DEBUG_PKG=2 env var and share the run output as well

   cc @faulpeltz
2. faulpeltz commented on Oct 16, 2025

   

   faulpeltz

   on Oct 16, 2025

   Last edited by faulpeltz

   More actions

   Cross compilation from and to macOS (without --public) doesnt work since Node 22 and I wasn't able to fix this in the latest Node 24 changes...
   Basically the code cache generated is not compatible between many OS/arch combinations because the V8 readonly heap snapshots are no longer the same - in Node 20 and earlier this works fine

   👍React with 👍1Reacted by Niek van der Maas
3. Niek commented on Oct 16, 2025

   

   Niek

   on Oct 16, 2025

   Author

   More actions

   There is no package.json, see the reproducible script in a fresh dir.

   ❯ npx -y @yao-pkg/pkg hello.js -t node22-linux-arm64 -o hello --debug
   > pkg@6.9.0
   > [debug] Bytecode of /Users/niek/test/hello.js is added to queue.
   > [debug] Stat info of /Users/niek/test/hello.js is added to queue.
   > [debug] Directory /Users/niek/test is added to queue.
   > [debug] Stat info of /Users/niek/test is added to queue.
   > [debug] Directory /Users/niek is added to queue.
   > [debug] Stat info of /Users/niek is added to queue.
   > [debug] Directory /Users is added to queue.
   > [debug] Stat info of /Users is added to queue.
   > [debug] Directory / is added to queue.
   > [debug] Stat info of / is added to queue.
   > [debug] Deleting record file: /
   > [debug] Deleting record file: /Users
   > [debug] The file was included as bytecode (no sources)
     /Users/niek/test/hello.js
   > [debug] The file was included as bytecode (no sources)
     /Users/niek/test/hello.js
   > [debug] files & folders deduped =
     hello.js
   > [debug] The directory files list was included (1 item)
     /Users/niek/test
   > [debug] The directory files list was included (1 item)
     /Users/niek/test
   > [debug] files & folders deduped =
     test
   > [debug] The directory files list was included (1 item)
     /Users/niek
   > [debug] The directory files list was included (1 item)
     /Users/niek
   > [debug] Targets:
     [
     {
       "nodeRange": "node22",
       "platform": "linux",
       "arch": "arm64",
       "output": "/Users/niek/test/hello",
       "forceBuild": false,
       "fabricator": {
         "nodeRange": "node22",
         "platform": "macos",
         "arch": "arm64",
         "binaryPath": "/Users/niek/.pkg-cache/v3.5/fetched-v22.20.0-macos-arm64-signed"
       },
       "binaryPath": "/Users/niek/.pkg-cache/v3.5/fetched-v22.20.0-linux-arm64"
     }
   ]
   ❯ docker run --rm -it -v $(pwd):/mnt -e DEBUG_PKG=2 ubuntu:latest /mnt/hello
   []
   ------------------------------- virtual file system
   /snapshot
     test                                    27 Bytes
       hello.js                              27 Bytes
   Total size =  27 Bytes
   fs.existsSync [ '/snapshot/test/hello.js' ]
   fs.statSync [ '/snapshot/test/hello.js' ]
   fs.readSync []
   fs.realpathSync [ '/snapshot/test/hello.js' ]
   fs.readFileSync [ '/snapshot/test/hello.js', 'utf8' ]
   fs.readSync []
4. Niek commented on Oct 16, 2025

   

   Niek

   on Oct 16, 2025

   Author

   More actions

   Cross compilation from and to macOS (without --public) doesnt work since Node 22 and I wasn't able to fix this in the latest Node 24 changes... Basically the code cache generated is not compatible between many OS/arch combinations because the V8 readonly heap snapshots are no longer the same

   Ah, that makes sense then. Might be worth adding a note to the README with this info (at least until there is a fix)?
5. faulpeltz commented on Oct 16, 2025

   

   faulpeltz

   on Oct 16, 2025

   More actions

   Yes but currently its unfortunately trial and error to sort out which versions are compatible or not. (currently linux/win/linuxstatic x64 seems to work)
   This behavior is caused by the new V8 versions included in Node and is probably not fixable because V8 code cache / snapshot data is not designed to be portable.

   If you don't mind including your source bundle (with --public) than this restriction does not apply because the code cache is discarded by Node when its not valid for the current binary and it falls back to the source.

   👀React with 👀1Reacted by Daniel Lando
6. robertsLando commented on Oct 16, 2025

   

   robertsLando

   on Oct 16, 2025

   Member

   More actions

   I added it here: #87
7. robertsLando

   added 5 commits that reference this issue on Apr 15, 2026

   docs: clarify cross-compile support and Node 22 regression

   ...

   2d1a352

   docs: host documentation on GitHub Pages with VitePress (#234)

   ...

   22fc2ed

   fix: fall back to source on bytecode fabrication failure

   ...

   46a7f8e

   feat: add --fallback-to-source flag for bytecode compilation failures

   ...

   c16577e

   feat: add --fallback-to-source flag for bytecode failures (#246)

   ...

   5eb4681
8. rejetto commented on May 24, 2026

   

   rejetto

   on May 24, 2026

   More actions

   with latest version, from macos arm to linux arm, i had to add --public-packages "*"