fix(process): improve error message for process.cwd() when directory is deleted

[Ankush1oo8]

This PR improves the error message thrown by process.cwd() when the current working directory is deleted. Instead of throwing a new error, it enhances the original error message, making it clearer that the directory was deleted while the process was still inside it.

Changes Made:

• Modified wrappedCwd() to enhance the existing error message for ENOENT: uv_cwd instead of creating a new Error instance.
• Ensured the error message explicitly states the reason and how to resolve it (using process.chdir() to switch directories).

Before (Old Behavior):

When the working directory was deleted, process.cwd() threw a generic error with little context:

Error: ENOENT: no such file or directory, uv_cwd

After (New Behavior):

Now, the error provides a more meaningful message:

Error: Current working directory does not exist - this can happen if the directory was deleted while the process was still inside it. Original error: ENOENT: no such file or directory, uv_cwd

Relevant Issue:

(If this PR fixes an issue, add the issue number here)
Example: Fixes#57045

PR-URL:

#57184

Reviewer Notes:

-added to docs

• added test js file
• Please review and let me know if further refinements are needed!

[Ankush1oo8]

@jasnell can you check this i have done some thing that caused deletion of repo can you now check the pr

[Ankush1oo8]

Are there more changes to make

[Ankush1oo8]

@aduh95 can you check for further process to approve

[aduh95]

Any reason you're not taking any of my suggestions? It's certainly fine if you disagree with those, but please at least comment on each explaining why

[Ankush1oo8]

Ohh sorry I think I made the changes but did not commit

[Ankush1oo8]

@aduh95 i have made changes according to your suggesations

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.15%. Comparing base (4acb854) to head (bf901af).
⚠️ Report is 1957 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #57184 +/- ##
=======================================
Coverage 90.15% 90.15% =======================================
Files 630 630 Lines 186756 186759 +3 Branches 36648 36651 +3 =======================================
+ Hits 168362 168370 +8 - Misses 11193 11201 +8 + Partials 7201 7188 -13 

Files with missing lines	Coverage Δ
src/node_errors.h	87.50% <ø> (ø)
src/node_process_methods.cc	87.50% <100.00%> (-0.36%)	⬇️

... and 42 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.

[Ankush1oo8]

can anyone tell me what should i do now

[addaleax]

@Ankush1oo8 As you can see, GH does point at failures in another test that are definitely related to this change – the exit code is now different in at least one case (test/parallel/test-cwd-enoent-preload.js). You'll need to debug why that particular problem occurs – it's probably a regression of the fix that originally introduced that test file, 2d251e6.

[Ankush1oo8]

@Ankush1oo8 As you can see, GH does point at failures in another test that are definitely related to this change – the exit code is now different in at least one case (test/parallel/test-cwd-enoent-preload.js). You'll need to debug why that particular problem occurs – it's probably a regression of the fix that originally introduced that test file, 2d251e6.

Can you check now

[Ankush1oo8]

@addaleax I don't know what to doi have tried to solve it but did not get any clue

[Ankush1oo8]

i have tried to change the code in test-cwd-enoent-preload.js
I think this can solve the cli test

[aduh95]

There are lint errors to address

[Ankush1oo8]

what should i do about first commit message @aduh95 can help please

[pmarchini]

Hey @Ankush1oo8, please rewrite your commit history so that it includes only one commit that passes the validations provided here: https://github.com/nodejs/core-validate-commit

[aduh95]

what should i do about first commit message

The first commit message is not blocking the merge, whoever lands this can fix that for you. However, the failing tests are blocking, we need to have the tests pass before this can land.

[legendecas]

I don't think this needs a new semver-major error code.

The original issue #57045 was saying that:

Could be made clearer that this is a failure of process.cwd() as the stack trace makes no mention of it

This is because the stack frame is named as the following. And the error message already said that the cwd is not a file or directory.

Error: ENOENT: no such file or directory, uv_cwd
at process.wrappedCwd [as cwd] (node:internal/bootstrap/switches/does_own_process_state:142:28)

We could just rename the function wrappedCwd to be cwd, and it will solve the issue.

[Renegade334]

The associated issue has now been closed, but thanks for the PR!