EnvSync-LE
Compare the dotenv files in a tree, and say which keys are missing from which
No editor in the loop? npx -y envsync-le-mcp runs the same engine as an MCP server, so an agent can call compare_env_files with nothing else installed, and cargo install envsync-le puts the same check in a terminal. Every way to install it.
Overview
What EnvSync-LE does
Environment files drift the moment one of them gains a key. EnvSync-LE compares the variable names across the .env files in your workspace and tells you which file is missing which key — names only, never values. Checks run automatically when a watched file changes, and the current issue count sits in the status bar.
What people use it for
Automatic checks
A debounced sync check runs whenever a watched .env file changes — no command to remember.
Three comparison modes
auto compares against the union of all keys, manual only the files you list, template validates everything against one reference file.
Names, never values
The report lists missing keys by name. The values in a .env file are exactly what should not be copied around.
Palette
9 commands
Open the command palette and type the name. Nothing is bound to a shortcut by default — the editor's keymap is the user's, not ours.
- Open Settings
envsync-le.openSettings - Show Details
envsync-le.showIssues - Compare Files
envsync-le.compareSelected - Set Template
envsync-le.setTemplate - Clear Template
envsync-le.clearTemplate - Ignore File
envsync-le.ignoreFile - Unignore File
envsync-le.stopIgnoring - Clear Ignored Files
envsync-le.clearAllIgnored - Help & Troubleshooting
envsync-le.help
Install
Install EnvSync-LE
VS Code
ext install nolindnaidoo.envsync-leOpen Quick Open (Cmd/Ctrl+P) and paste.
Cursor / Windsurf
cursor --install-extension nolindnaidoo.envsync-leCursor, Windsurf, VSCodium and the other VS Code forks pull from Open VSX. The id is the same as on the Marketplace.
AI agents
npx -y envsync-le-mcpRuns EnvSync-LE's engine as an MCP server, so an agent can call compare_env_files with no editor involved. VS Code 1.101+ needs nothing — the extension registers it for you.
Channels
Where it ships
One engine, 5 places to get it. Copy the one for the editor you use.
Links
Where EnvSync-LE lives
- VS Code Marketplaceenvsync-le
- Open VSXfor Cursor, Windsurf and VSCodium
- npmenvsync-le-mcp
- GitHubsource, issues, changelog
- MCP registryio.github.nolindnaidoo/envsync-le
The family
The other 16
String-LEExtract every string in a codebase, so a person can read them
Numbers-LEExtract every hardcoded number in a codebase, so a person can check them
Paths-LEExtract every file path in a codebase, and say whether it still points at anything
Colors-LEExtract every color in a codebase, and say which ones are not in your palette
URLs-LEExtract every URL in a codebase, with its protocol and exact position
Dates-LEExtract every date and timestamp, and the exact instant each one resolves to
Units-LEExtract every quantity with its unit, normalized, and refuse the ambiguous ones by name
IDs-LEExtract every UUID, ULID, NanoID, ObjectId and Snowflake, and decode the time inside
IPs-LEExtract every IP address, CIDR block and MAC, normalized and classified by scope
Regex-LEFind every regex in a codebase, and report which can be driven into catastrophic backtracking
Scrape-LECheck whether a page is scrapeable before the scraper is written, and say when it cannot tell
Versions-LEFind where one dependency is constrained differently across a repository's manifests
i18n-LEIdentify the i18n library a project uses, then audit its catalogs by that library's rules
DecisionLintLint Jev and Luna questions before they are sent: the questions you write for TypeSafe's Jev, OpenAI's Decisions API (gpt-6-luna) or any platform that serves one, as you type, with no API key and no network calls. An optional command asks the model itself to check a file
Secrets-LEFind hardcoded credentials in a codebase, and never print one into the report
Unicode-LEFind the Unicode that hides meaning — bidi controls, invisibles, homoglyphs, mixed scripts