Skip to content

Conversation

@Jeevankumar-s
Copy link
Contributor

@Jeevankumar-s Jeevankumar-s commented Jan 13, 2026

This PR clarifies the behavior of process.argv[1] when Node.js is run in
no-script execution modes such as -e / --eval.

Fixes: #61363

Signed-off-by: Jeevankumar-S <jeevenkumar2003@email.com>
@nodejs-github-bot nodejs-github-bot added doc Issues and PRs related to the documentations. process Issues and PRs related to the process subsystem. labels Jan 13, 2026
@aduh95
Copy link
Contributor

aduh95 commented Jan 17, 2026

Can you please restore the line wrapping so this can be reviewed?

@Jeevankumar-s
Copy link
Contributor Author

Can you please restore the line wrapping so this can be reviewed?

Thanks for the review! I’ve restored the line wrapping to match the original documentation style. Please take another look.

@aduh95
Copy link
Contributor

aduh95 commented Jan 17, 2026

Linter failures to address

4540:1-4540:52 warning Unordered reference ("Permission Model" should be before "program entry point")      nodejs-links  remark-lint
4604:72        warning Unexpected missing final newline character, expected line feed (`\n`) at end of file final-newline remark-lint

@Jeevankumar-s
Copy link
Contributor Author

Linter failures to address

4540:1-4540:52 warning Unordered reference ("Permission Model" should be before "program entry point")      nodejs-links  remark-lint
4604:72        warning Unexpected missing final newline character, expected line feed (`\n`) at end of file final-newline remark-lint

I’ve reordered the reference links and added the missing final newline to address the markdown linter warnings

@Jeevankumar-s Jeevankumar-s requested a review from aduh95 January 18, 2026 07:05
@Jeevankumar-s
Copy link
Contributor Author

Hi @aduh95 , for this lint warning, is it better to reorder the reference links or capitalize [program entry point]?

@aduh95
Copy link
Contributor

aduh95 commented Jan 18, 2026

Capitalization wouldn't make sense here IMO, reordering seems more logical

@Jeevankumar-s
Copy link
Contributor Author

Capitalization wouldn't make sense here IMO, reordering seems more logical

I’ll reorder the links accordingly.

@aduh95 aduh95 added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue Add this label to land a pull request using GitHub Actions. commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. labels Jan 21, 2026
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Jan 21, 2026
@nodejs-github-bot nodejs-github-bot merged commit 7d0417f into nodejs:main Jan 21, 2026
27 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in 7d0417f

@Jeevankumar-s Jeevankumar-s deleted the doc-process-argv-eval branch January 21, 2026 09:36
aduh95 pushed a commit that referenced this pull request Jan 22, 2026
Signed-off-by: Jeevankumar-S <jeevenkumar2003@email.com>
PR-URL: #61366
Fixes: #61363
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. doc Issues and PRs related to the documentations. process Issues and PRs related to the process subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

doc: clarify process.argv[1] behavior for -e/--eval

3 participants