String-LE
Extract string values from JSON, YAML, CSV, TOML, INI, and .env — for i18n.
What String-LE does
Locale files, config files and CSV exports all bury their string values in structure. String-LE flattens that structure away: run one command and every string value in the document lands in a new editor, ready to paste into a translation tool or scan by eye. It parses JSON, YAML, CSV, TOML, INI and .env, and streams large CSVs rather than loading them whole.
What people use it for
i18n prep
Flatten locale files into a clean list of translatable values, without the key hierarchy in the way.
Config review
See every string value in a TOML, INI or .env file at a glance.
CSV mining
Pull one column, several, or all of them — large files stream rather than loading whole.
Install String-LE
VS Code
ext install nolindnaidoo.string-leOpen Quick Open (Cmd/Ctrl+P) and paste.
Cursor / VSCodium
cursor --install-extension OffensiveEdge.string-leVS Code forks pull from Open VSX, where the namespace is OffensiveEdge.
ZedComing soon
npx -y string-le-mcpWorks in Zed today — add the command above as a custom MCP server from the agent panel, and extract_strings 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 string-le-mcpRuns String-LE's engine as an MCP server, so an agent can call extract_strings with no editor involved. VS Code 1.101+ needs nothing — the extension registers it for you.
Where String-LE lives
- VS Code Marketplacestring-le
- Open VSXfor Cursor and VSCodium
- GitHubsource, issues, changelog
- npmstring-le-mcp
- MCP registryio.github.nolindnaidoo/string-le
The other nine
Extract numeric values from JSON, YAML, CSV, TOML, INI, and .env.
Pull every file path out of JS/TS imports, JSON, HTML, CSS, TOML, CSV, and .env files.
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.