docs(npx): clarify that arguments are passed to executed command

[MaxBlack-dev]

Description

This PR adds clarification to the npx documentation about how arguments and options are handled when executing commands.

Changes

• Added a clear explanation that arguments after the package name are passed directly to the executed command, not to npx
• Included a practical example (npx create-react-app my-app --template typescript)
• Directed users to consult package-specific documentation for available options

Fixes

Closes#7186

Context

Users were confused about where options like --use-npm and --example come from when running commands like npx 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:

1. Arguments after the package name go to the executed command
2. npx options must come before the package name
3. Package-specific options should be looked up in that package's documentation

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

• Documentation update

[MaxBlack-dev]

Description

This PR adds clarification to the npx documentation about how arguments and options are handled when executing commands.

Changes

• Added a clear explanation that arguments after the package name are passed directly to the executed command, not to npx
• Included a practical example (npx create-react-app my-app --template typescript)
• Directed users to consult package-specific documentation for available options

Fixes

Closes#7186

Context

Users were confused about where options like --use-npm and --example come from when running commands like npx 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:

1. Arguments after the package name go to the executed command
2. npx options must come before the package name
3. Package-specific options should be looked up in that package's documentation

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

• Documentation update

[MaxBlack-dev]

Description

This PR adds clarification to the npx documentation about how arguments and options are handled when executing commands.

Changes

• Added a clear explanation that arguments after the package name are passed directly to the executed command, not to npx
• Included a practical example (npx create-react-app my-app --template typescript)
• Directed users to consult package-specific documentation for available options

Fixes

Closes#7186

Context

Users were confused about where options like --use-npm and --example come from when running commands like npx 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:

1. Arguments after the package name go to the executed command
2. npx options must come before the package name
3. Package-specific options should be looked up in that package's documentation

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

• Documentation update

[MaxBlack-dev]

Description

This PR adds clarification to the npx documentation about how arguments and options are handled when executing commands.

Changes

• Added a clear explanation that arguments after the package name are passed directly to the executed command, not to npx
• Included a practical example (npx create-react-app my-app --template typescript)
• Directed users to consult package-specific documentation for available options

Fixes

Closes#7186

Context

Users were confused about where options like --use-npm and --example come from when running commands like npx 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:

1. Arguments after the package name go to the executed command
2. npx options must come before the package name
3. Package-specific options should be looked up in that package's documentation

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

• Documentation update

[MaxBlack-dev]

Description

This PR adds clarification to the npx documentation about how arguments and options are handled when executing commands.

Changes

• Added a clear explanation that arguments after the package name are passed directly to the executed command, not to npx
• Included a practical example (npx create-react-app my-app --template typescript)
• Directed users to consult package-specific documentation for available options

Fixes

Closes#7186

Context

Users were confused about where options like --use-npm and --example come from when running commands like npx 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:

1. Arguments after the package name go to the executed command
2. npx options must come before the package name
3. Package-specific options should be looked up in that package's documentation

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

• Documentation update

[MaxBlack-dev]

Description

This PR adds clarification to the npx documentation about how arguments and options are handled when executing commands.

Changes

• Added a clear explanation that arguments after the package name are passed directly to the executed command, not to npx
• Included a practical example (npx create-react-app my-app --template typescript)
• Directed users to consult package-specific documentation for available options

Fixes

Closes#7186

Context

Users were confused about where options like --use-npm and --example come from when running commands like npx 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:

1. Arguments after the package name go to the executed command
2. npx options must come before the package name
3. Package-specific options should be looked up in that package's documentation

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

• Documentation update

[MaxBlack-dev]

Description

This PR adds clarification to the npx documentation about how arguments and options are handled when executing commands.

Changes

• Added a clear explanation that arguments after the package name are passed directly to the executed command, not to npx
• Included a practical example (npx create-react-app my-app --template typescript)
• Directed users to consult package-specific documentation for available options

Fixes

Closes#7186

Context

Users were confused about where options like --use-npm and --example come from when running commands like npx 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:

1. Arguments after the package name go to the executed command
2. npx options must come before the package name
3. Package-specific options should be looked up in that package's documentation

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

• Documentation update

[MaxBlack-dev]

Description

This PR adds clarification to the npx documentation about how arguments and options are handled when executing commands.

Changes

• Added a clear explanation that arguments after the package name are passed directly to the executed command, not to npx
• Included a practical example (npx create-react-app my-app --template typescript)
• Directed users to consult package-specific documentation for available options

Fixes

Closes#7186

Context

Users were confused about where options like --use-npm and --example come from when running commands like npx 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:

1. Arguments after the package name go to the executed command
2. npx options must come before the package name
3. Package-specific options should be looked up in that package's documentation

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

• Documentation update