Paths-LE
Pull every file path out of JS/TS imports, JSON, HTML, CSS, TOML, CSV, and .env files.
What Paths-LE does
A path in an import, an asset reference or a config value is a dependency you cannot see until something breaks. Paths-LE extracts every file and directory path from the active document and classifies each one, so a refactor or an asset audit starts from a list rather than a search. It reads JS/TS imports including multi-line statements, HTML and CSS references, and JSON, TOML, CSV and .env values.
What people use it for
Import analysis
Extract local imports from JS/TS, including multi-line statements — npm package names are filtered out.
Asset auditing
Every src, href, srcset, url() and @import in your HTML and CSS.
Config review
Path-like values from JSON, JSONC, TOML, CSV and .env files.
Install Paths-LE
VS Code
ext install nolindnaidoo.paths-leOpen Quick Open (Cmd/Ctrl+P) and paste.
Cursor / VSCodium
cursor --install-extension OffensiveEdge.paths-leVS Code forks pull from Open VSX, where the namespace is OffensiveEdge.
ZedComing soon
npx -y paths-le-mcpWorks in Zed today — add the command above as a custom MCP server from the agent panel, and extract_paths appears in its tool list. The one-click listing in Zed's extension registry is a pull request awaiting review. Track the review.
AI agents
npx -y paths-le-mcpRuns Paths-LE's engine as an MCP server, so an agent can call extract_paths with no editor involved. VS Code 1.101+ needs nothing — the extension registers it for you.
Where Paths-LE lives
- VS Code Marketplacepaths-le
- Open VSXfor Cursor and VSCodium
- GitHubsource, issues, changelog
- npmpaths-le-mcp
- MCP registryio.github.nolindnaidoo/paths-le
The other nine
Extract string values from JSON, YAML, CSV, TOML, INI, and .env — for i18n.
Extract numeric values from JSON, YAML, CSV, TOML, INI, and .env.
Extract and analyze colors from CSS, SCSS, LESS, Stylus, HTML, JS/TS, and SVG.
Extract URLs from documentation, configs, and code.
Extract date and time data from logs, configs, and code.
Find, test, and validate the regular expressions in any file — match reports and built-in ReDoS screening.
Check whether a page is actually scrapeable before you burn hours debugging.
Detect and sanitize credentials, tokens, API keys, and private keys locally — before you commit.
Spot missing keys across your .env files — automatic checks, a status bar counter, and a markdown report.