Optimize the search logic for launch.json #1252

Activity

1. Jinbo Wang (testforstephen)

   added

   debt

   on Feb 10, 2023
2. github-actions commented on Nov 10, 2025

   

   github-actionsBot

   on Nov 10, 2025 – with GitHub Actions

   More actions

   Hi Jinbo Wang (@testforstephen), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

   Here’s how you can optimize your launch.json lookup:

   • Scope to a single folder and limit results

     import { RelativePattern, workspace, WorkspaceFolder } from 'vscode';
     
     async function findLaunchJson(folder: WorkspaceFolder) {
       // only look under the workspace folder’s .vscode folder, stop after the first match
       const pattern = new RelativePattern(folder, '.vscode/launch.json');
       const results = await workspace.findFiles(pattern, '**/node_modules/**', 1);
       return results[0];
     }

   • If you don’t need a RelativePattern, you can still pass maxResults directly:

     const [file] = await workspace.findFiles(
       '.vscode/launch.json',
       '**/node_modules/**',
       1
     );

   Other references worth checking:

   Low-confidence reference

   • The VS Code Java extension historically searched entire workspaces for files and was optimized by using RelativePattern to limit each folder’s scope. see issue comment: The system become extremely slow when loading a huge Java workspace redhat-developer/vscode-java#1236 (comment)

   The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
3. github-actions

   added

   ai-triaged

   enhancement

   on Nov 10, 2025