Fix npx command parsing to support --yes and -y flags#2299
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Contributor
|
Agentic Changeset Generator triggered by this pull request. |
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix npx command parsing for --yes and -y flags
Fix npx command parsing to support --yes and -y flags
Oct 24, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
The npx package validation was incorrectly treating flags like
-yand--yesas package names. When compiling workflows, the output showed:This occurred in three scenarios:
npx -y @github/copilot@0.0.350mcp: "npx -y @modelcontextprotocol/server-filesystem /tmp"command: npx, args: ["-y", "@microsoft/markitdown"]Solution
Updated the npx command parsing to skip flag arguments before extracting package names, following the same pattern used by the existing
extractUvFromCommandsandextractPipFromCommandsfunctions.Changes
pkg/workflow/npm.go- ModifiedextractNpxFromCommands()to iterate through words afternpxand skip any arguments starting with-or--:pkg/workflow/validation.go- UpdatedcollectPackagesFromWorkflow()to:pkg/workflow/runtime_setup.go- ExtendeddetectFromMCPConfigs()to handle string-format MCP tools, ensuring Node.js runtime is detected for workflows usingnpxcommandspkg/workflow/validation_test.go- Added test coverage for:npx with -y flagnpx with --yes flagnpx with multiple flagsnpx with flags and shell operatorsResults
After the fix, package validation correctly identifies the actual packages:
All existing tests pass, and the new test cases ensure proper handling of npx flags across different workflow formats.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.