vscode-config-generator

To generate VS Code launch.json and tasks.json configurations, the tool detects project stacks like Node, .NET, or Python using markers such as package.json or pyproject.toml. It then applies matching templates and presents a diff for user confirmation before writing.

Yes, you can auto-generate VS Code debug configs for mixed monorepos. The tool detects multiple stacks simultaneously, selects the matching templates for each, and merges them into a unified configuration while preserving existing hand-written entries.

Generating new VS Code task configs will not overwrite existing .vscode files. The tool merges generated entries with your current configurations, preserving hand-written entries and marking generated items with a detail tag for traceability.

Supported project stacks for VS Code debug and task setup include Node, .NET, and Python. The tool detects these by looking for specific stack markers like package.json, *.csproj, pyproject.toml, or requirements.txt in your repository.

The best way to update launch configurations across a team repository is to auto-generate them using detected stacks. The tool merges new entries with existing .vscode files, marks generated items for traceability, and presents a diff to ensure consistent debugging setups for all developers.

Yes, you need to manually review generated .vscode configurations before applying them. The tool presents a proposed diff of the tasks.json and launch.json entries, allowing you to confirm the changes and ensuring hand-written entries are preserved.