- 
                Notifications
    
You must be signed in to change notification settings  - Fork 133
 
Fix npm package installation to check appropriate files based on command #711
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Merged
      
      
    Conversation
  
    
      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
    
  
  
    
    Co-authored-by: aaronpowell <[email protected]>
Co-authored-by: aaronpowell <[email protected]>
Co-authored-by: aaronpowell <[email protected]>
      
          
Copilot
AI
        changed the title
[WIP] The 
Fix npm package installation to check appropriate files based on command
      Jun 4, 2025 
    
  WithNpmPackageInstallation API assumes that packages have already been installed    
          Copilot finished work on behalf of 
  aaronpowell 
    June 4, 2025 01:19     
    
              
                    aaronpowell
  
              
              approved these changes
              
                  
                    Jun 4, 2025 
                  
              
              
            
            
          
 Minimum allowed line rate is   | 
    
              
                    aaronpowell
  
              
              approved these changes
              
                  
                    Jun 4, 2025 
                  
              
              
            
            
  This was referenced Aug 5, 2025 
      
  This was referenced Aug 27, 2025 
      
  
    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.
  
    
  
    
The
WithNpmPackageInstallationAPI was incorrectly requiringpackage-lock.jsonfor all npm operations, includingnpm installwhich only needspackage.json. This caused failures in common developer workflows where developers create apackage.jsonfile but haven't runnpm installyet.Problem
When using the default configuration:
The application would fail with:
This occurred even when using
npm install(notnpm ci), which should work with justpackage.json.Solution
Modified
NodePackageInstaller.PerformInstall()to conditionally check for different files based on the install command:installCommand == "ci": checks for lockfile (package-lock.json) - preserves existing behaviorinstallCommand == "install": checks forpackage.json- new behavior that fixes the issueKey Benefits
✅
npm installnow works when onlypackage.jsonexists (common developer workflow)✅
npm cistill requirespackage-lock.json(correct behavior)✅ Error messages clearly indicate which file is missing based on the command
✅ No breaking changes to existing APIs
✅ Consistent with how npm actually works
Testing
Added comprehensive tests to validate both scenarios work correctly and error messages are appropriate.
Fixes #618.
Warning
Firewall rules blocked me from connecting to one or more addresses
I tried to connect to the following addresses, but was blocked by firewall rules:
dnceng.pkgs.visualstudio.comdotnet build src/CommunityToolkit.Aspire.Hosting.NodeJS.Extensions/CommunityToolkit.Aspire.Hosting.NodeJS.Extensions.csproj(dns block)dotnet build src/CommunityToolkit.Aspire.Hosting.NodeJS.Extensions/CommunityToolkit.Aspire.Hosting.NodeJS.Extensions.csproj -f net8.0(dns block)download.visualstudio.microsoft.comwget REDACTED -O /tmp/dotnet-9.tar.gz(dns block)http://168.63.129.16:80/machine//usr/bin/python3 -u bin/WALinuxAgent-2.13.1.1-py3.9.egg -collect-logs(http block)If you need me to access, download, or install something from one of these locations, you can either:
💡 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.