Skip to content

SIGABRT after node cli start #61817

@chrisschnei

Description

@chrisschnei

Version

v25.6.1

Platform

Darwin MacBook-Pro.local 24.6.0 Darwin Kernel Version 24.6.0: Wed Nov  5 21:30:23 PST 2025; root:xnu-11417.140.69.705.2~1/RELEASE_X86_64 x86_64

Subsystem

No response

What steps will reproduce the bug?

Install node via brew. Execute "node" command in shell (zsh, bash).

How often does it reproduce? Is there a required condition?

On every execution. The issue also occurs with different node versions.

What is the expected behavior? Why is that the expected behavior?

After executing node command the node shell should start.

What do you see instead?

MacBook-Pro bin % node

:
(Use node --trace-uncaught ... to show where the exception was thrown)

Node.js v25.6.1

MacBook-Pro bin % node --trace-uncaught

:

Node.js v25.6.1

MacBook-Pro bin % echo $?
6

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions