cross-platform-paths Skill

Source

• Creator: microsoft
• Repository: microsoft/vscode-python-environments
• Skill file: .github/skills/cross-platform-paths/SKILL.md

What it does

Critical patterns for cross-platform path handling in this VS Code extension. Windows vs POSIX path bugs are the 1 source of issues. Use this skill when reviewing or writing path-related code.

Skill instructions

Cross-Platform Path Handling CRITICAL: This extension runs on Windows, macOS, and Linux. Path bugs are the 1 source of issues. Core Rules Rule 1: Never Concatenate Paths with / typescript // ❌ WRONG: POSIX-style path concatenation const envPath = homeDir + '/.venv/bin/python'; // ✅ RIGHT: Use path.join() const envPath = path.join(homeDir, '.venv', 'bin', 'python'); Rule 2: Use path.resolve() for Comparisons, Not path.normalize() typescript // ❌ WRONG: path.normalize keeps relative paths relative on Windows const normalized = path.normalize(fsPath); // path.normalize('\test') → '\test' (still relative!) // ✅ RIGHT: path.resolve adds drive letter on Windows const normalized = path.resolve(fsPath); // path.resolve('\test') → 'C:\test' (absolute!) // When comparing paths, use resolve() on BOTH sides: const pathA = path.resolve(fsPath); const pathB = path.resolve(e.environmentPath.fsPath); return pathA === pathB; Rule 3: Use Uri.file().fsPath for VS Code Paths typescript // ❌ WRONG: Raw str