Node command doesn't work on MacOS Sequoia

[mathis-lambert]

Version

v22.3.0

Platform

Darwin macbookpro.home 24.0.0 Darwin Kernel Version 24.0.0: Thu May 30 21:30:12 PDT 2024; root:xnu-11215.0.31.511.2~1/RELEASE_ARM64_T6000 arm64

Subsystem

NodeJS

What steps will reproduce the bug?

On MacOS Sequoia, execute node index.js on a javascript file, and then it does nothing...

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

Everytime

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

The expected behavior is to run the javascript file ...

What do you see instead?

void

Additional information

Do you have some tools to debug what's happening during the node command ?

[RedYetiDev]

@nodejs/platform-macos Does the Node.js provide support for Apple's Developer Beta Program?

https://www.apple.com/macos/macos-sequoia-preview/

[RedYetiDev]

@mathis-lambert For debugging, you can run NODE_DEBUG=* node index.js

[mathis-lambert]

Well i guess, its very long to load the modules, but after 5 minutes it seems to have started
Like, look at this : 45s to load a directory

[mathis-lambert]

Oh well now when im doing node index.js, it's starting within a second.
That's weird

[aduh95]

What's the output of node -p '2+2'? Is your app any faster on a different system?

[mathis-lambert]

@aduh95 the output is 4, and yeah my app starts within a second on other systems.
I also want to point out that, i reinstall Node with brew and run npm i on my project.
For the first time i start my application it takes so much time (imports are slow ?) but now my app is running fast and node -p "2+2" is also fast to print...
Maybe a bad behavior on MacOS Sequoia side ? but it happens to me only with NodeJS

[AntiMoron]

maybe it's filesystem issue. Have you ever tried to npm install? Seems like it's requiring package semver.

Well i guess, its very long to load the modules, but after 5 minutes it seems to have started Like, look at this : 45s to load a directory

[RedYetiDev]

It's possible. I have a sequoia MacBook, so when I get back-in-town, I'll test some benchmarks with the debug build.