process: add process.entrypoint

[avivkeller]

Ref: #51840

Adds a process.entrypoint non-configurable property to the process object during bootstrap. This property reflects the executable's main entrypoint (i.e. not --require or --import-ed files, the main file).

Additionally, this entrypoint is passed to workers, so it reflects the entrypoint of the process that created the worker, not the entrypoint of the worker itself.

[nodejs-github-bot]

Review requested:

• @nodejs/loaders

[avivkeller]

@nodejs/process

[mcollina]

in worker threadsx this is set to the entrypoint of the worker?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.27%. Comparing base (6a3d80f) to head (cd95cbd).
⚠️ Report is 101 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #64800      +/-   ##
==========================================
+ Coverage   90.16%   90.27%   +0.10%     
==========================================
  Files         744      762      +18     
  Lines      242518   247563    +5045     
  Branches    45705    46699     +994     
==========================================
+ Hits       218670   223483    +4813     
- Misses      15357    15502     +145     
- Partials     8491     8578      +87     

Files with missing lines	Coverage Δ
lib/internal/main/worker_thread.js	94.42% <100.00%> (+0.07%)	⬆️
lib/internal/process/pre_execution.js	97.11% <100.00%> (-0.85%)	⬇️
lib/internal/worker.js	96.75% <100.00%> (+<0.01%)	⬆️

... and 134 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[avivkeller]

in worker threadsx this is set to the entrypoint of the worker?

This is set to the entrypoint of the process that created the worker, not the worker itself. So if /my/path/index.js creates /my/worker/index.js, entrypoint will a URL of /my/path/index.js.

[mcollina]

in worker threadsx this is set to the entrypoint of the worker?

This is set to the entrypoint of the process that created the worker, not the worker itself. So if /my/path/index.js creates /my/worker/index.js, entrypoint will a URL of /my/path/index.js.

this is behaviorally different from the old "require.main".

Can we have the same?

[avivkeller]

IMO it makes more sense to show the entrypoint of the process, not the worker

[mcollina]

I'm saying this is not identical to require.main, or what import.main is defined.

The issue linked refers to require.main.

[avivkeller]

Okay, I've changed Fixes to Ref, since I feel that it makes more sense to show it this way

[mcollina]

Opened #64903 with the thread-scoped counterpart (module.entrypoint in node:module), matching require.main semantics.

[avivkeller]

Awesome! Aside from that, is this good to go?

[avivkeller]

bump @nodejs/process