macOS refuses to start `node` when downloaded from the tarball
Open
Nobody has claimed this yet.
help wanted
platform:macos
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
When I download that release into a arm mac running Sonoma 14.0 and then try to run ./bin/node using the terminal I'm getting a security notice that you can check in the following image
Originally posted by @mistic in https://github.com/nodejs/build/issues/3385#issuecomment-1769027175
Repro:
- Download the tarball with a web browser, for example using https://nodejs.org/download/release/latest-v18.x/node-v18.18.2-darwin-x64.tar.xz
cd ~/Downloads && tar xf node-v18.18.2-darwin-x64.tar.xz- Try to run
./node-v18.18.2-darwin-x64/bin/node
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the problem by downloading the node-v18.18.2-darwin-x64.tar.xz tarball, extracting it, and running its bin/node entry point from a terminal on macOS Sonoma. Investigate how the downloaded release artifact is handled by macOS, and consider the issue complete when the extracted node binary starts without the reported security notice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, node.js
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100