docs(npx): clarify that arguments are passed to executed command #8794
+2
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds clarification to the npx documentation about how arguments and options are handled when executing commands.
Changes
npx create-react-app my-app --template typescript)Fixes
Closes #7186
Context
Users were confused about where options like
--use-npmand--examplecome from when running commands likenpx create-next-app. As reported in issue #7186, the documentation didn't clearly explain that these options belong to the executed package (e.g.,create-next-app), not to npx itself.This clarification helps users understand:
While the existing documentation did cover this concept in the "npx vs npm exec" section with technical details, it wasn't immediately clear for new users in the Description section where they start reading.
Type of Change