Paths-LE: Zero Hassle Path Extraction

Instantly extract and analyze file paths from your codebase with precision
JavaScript, JSON, YAML, logs, configs, and more
Designed for file management, dependency analysis, and path validation.

Screenshot Guide

🙏 Thank You!

Thank you for your interest in Paths-LE! If this extension has been helpful in managing your path extraction needs, please consider leaving a rating on VS Code Marketplace and Open VSX. Your feedback helps other developers discover this tool and motivates continued development.

⭐ Interested in Paths-LE? Star this repository to get notified when it's released!

🚀 More from the LE Family

Paths-LE is part of a growing family of developer tools designed to make your workflow effortless:

• Strings-LE - Extract every user-visible string from JSON, YAML, CSV, TOML, INI, and .env files with zero hassle
  [VS Code Marketplace] [Open VSX]

• EnvSync-LE - Effortlessly detect, compare, and synchronize .env files across your workspace with visual diffs
  [VS Code Marketplace] [Open VSX]

• Numbers-LE - Extract and analyze numeric data from JSON, YAML, CSV, TOML, INI, and .env
  [VS Code Marketplace] [Open VSX]

• Colors-LE - Extract and analyze colors from CSS, SCSS, JavaScript, HTML, and more
  Coming October 2025

• Dates-LE - Extract and analyze dates from logs, JSON, YAML, CSV, and temporal data
  Coming October 2025

• URLs-LE - Extract and analyze URLs from HTML, Markdown, configs, and documentation
  Coming October 2025

Each tool follows the same philosophy: Zero Hassle, Maximum Productivity.

✅ Why Paths-LE

Modern applications reference files everywhere — imports, exports, configuration files, asset paths, and resource references. Keeping track of all file paths across your codebase can be overwhelming.

Paths-LE makes path extraction effortless.
It intelligently detects and extracts file paths from your code, providing comprehensive analysis and insights to help you manage file dependencies effectively.

• Complete path detection

  Automatically finds file paths in multiple formats: absolute paths, relative paths, Windows paths, and Unix paths.

• Smart analysis & insights

  Get detailed reports on path usage patterns, dependency analysis, and file reference distribution across your codebase.

• Dependency analysis support

  Perfect for analyzing imports, exports, and file references to identify missing files and circular dependencies.

• Reliable file format support

  Works with CSV, TOML, and Environment files using proven parsing libraries for 100% accuracy.

• Cross-platform compatibility

  Handles both Windows and Unix path formats with intelligent normalization and validation.

💡 Use Cases & Examples

Import/Export Analysis

Extract and analyze import statements in JavaScript projects:

// Extract from main.js
import { Component } from './components/Button'
import { utils } from '../utils/helpers'
import { config } from '/src/config/settings.json'

Asset Path Management

Identify all asset references in web projects:

<!-- Extract from index.html -->
<img src="https://github.com/nolindnaidoo/paths-le/raw/HEAD/assets/images/logo.png" alt="Logo" />
<link rel="stylesheet" href="./styles/main.css" />
<script src="../js/app.js"></script>

Configuration File Analysis

Extract file paths from configuration files:

# Extract from config.toml
[paths]
data_dir = "./data"
log_file = "/var/log/app.log"
backup_path = "C:\\backups\\app"

# Extract from paths.csv
path,type,description
./src/main.js,file,Main application file
/var/log/app.log,file,Application log
C:\Users\Name\data,dir,User data directory

Dependency Mapping

Map file dependencies and identify missing or broken references across your codebase.

🚀 Quick Start

1. Coming Soon - Paths-LE will be available on VS Code Marketplace and Open VSX
2. Open any file containing paths (Cmd/Ctrl + P Paths-LE)
3. Run Quick Extract (Cmd+Alt+E / Ctrl+Alt+E / Status Bar)

⚙️ Configuration

• paths-le.enabled – Enable or disable the extension
• paths-le.extractAbsolute – Extract absolute paths
• paths-le.extractRelative – Extract relative paths
• paths-le.extractWindows – Extract Windows paths
• paths-le.extractUnix – Extract Unix paths
• paths-le.includeComments – Include paths in comments
• paths-le.sortByFrequency – Sort results by usage frequency
• paths-le.groupByFormat – Group paths by format type
• paths-le.validatePaths – Enable path validation

🌍 Language Support

English + 12 translations (Coming Soon):

• Chinese (Simplified), Spanish, French, Russian, Portuguese (Brazil)
• Japanese, Korean, German, Italian, Vietnamese, Ukrainian, Indonesian

🧩 System Requirements

• VS Code: 1.85.0 or higher
• Node.js: Not required (extension runs in VS Code's built-in runtime)
• Platform: Windows, macOS, Linux
• Memory: 50MB minimum, 200MB recommended for large files
• Storage: 15MB for extension files

🧩 Compatibility

• Works in standard workspaces.
• Limited support in virtual/untrusted workspaces.

🔒 Privacy & Telemetry

• Runs locally; no data is sent off your machine.
• Optional local-only logs can be enabled with paths-le.telemetryEnabled.

⚡ Performance

Paths-LE is built for speed across all supported formats:

Performance Notes

• Memory Usage: ~50MB base + 1MB per 1000 paths processed
• Large Files: Files over 15MB may show reduced throughput (300K-800K paths/sec)
• Path Validation: Adds 20-30% processing time when enabled
• Cross-platform: Windows/Unix path normalization adds minimal overhead
• Hardware Requirements: Minimum 4GB RAM, recommended 8GB+ for large codebases

🔧 Troubleshooting

Common Issues

Extension not detecting paths

• Ensure file is saved and has a supported extension (.js, .json, .yaml, .ini, .log)
• Check that paths-le.enabled is set to true in settings
• Try reloading VS Code window (Ctrl/Cmd + Shift + P → "Developer: Reload Window")

Performance issues with large files

• Files over 10MB may take longer to process
• Consider using paths-le.includeComments: false to reduce processing time
• Enable paths-le.sortByFrequency: false for faster extraction

Paths not appearing in results

• Verify the path format is supported (absolute, relative, Windows, Unix)
• Check if paths-le.extractAbsolute, paths-le.extractRelative, etc. are enabled
• Ensure paths are not inside comments if paths-le.includeComments is disabled
• Check for proper path formatting and separators

Path validation issues

• Enable paths-le.validatePaths: true for path validation
• Check that paths exist in the workspace
• Verify path separators match your operating system
• Some paths may be valid but not accessible from the current workspace

Cross-platform compatibility problems

• Check paths-le.extractWindows and paths-le.extractUnix settings
• Ensure path normalization is working correctly
• Verify that mixed path formats are handled properly
• Some paths may be platform-specific and not valid on all systems

Extension crashes or freezes

• Check VS Code version compatibility (requires 1.85.0+)
• Disable other path-related extensions temporarily
• Check Output panel → "Paths-LE" for error messages

Getting Help

• Check the Issues page for known problems
• Enable telemetry logging: paths-le.telemetryEnabled: true
• Review logs in Output panel → "Paths-LE"

❓ FAQ

Q: What types of paths are extracted? A: Paths-LE extracts absolute paths (/usr/local/bin), relative paths (./src/components), Windows paths (C:\Users\Name), and Unix paths (/home/user).

Q: What file formats are supported? A: Paths-LE supports CSV, TOML, and Environment files (.env) using proven parsing libraries for 100% reliable extraction.

Q: Why only these formats? A: We prioritize "zero hassle" reliability. These formats use proper parsers instead of error-prone regex patterns, ensuring accurate results every time.

Q: How does path validation work? A: When paths-le.validatePaths: true is enabled, Paths-LE checks if the extracted paths exist in your workspace and reports any missing or invalid paths.

Q: Can I group paths by format type? A: Yes, enable paths-le.groupByFormat: true to organize results by path format (absolute, relative, Windows, Unix, etc.).

Q: Does Paths-LE work cross-platform? A: Absolutely! Paths-LE handles both Windows and Unix path formats with intelligent normalization and validation.

Q: What's the largest file size supported? A: Paths-LE can handle files up to 30MB, though performance may be reduced for very large files. Consider breaking large files into smaller chunks for better performance.

📊 Test Coverage

• Tests powered by Vitest with V8 coverage.
• Runs quickly and locally: npm run test or npm run test:coverage.
• Coverage reports output to coverage/ (HTML summary at coverage/index.html).

Copyright © 2025 @nolindnaidoo. All rights reserved.