CSEdge Environment Doctor – Enterprise Configuration Analysis
CSEdge Environment Doctor is a production-focused Visual Studio Code extension for detecting, explaining, and resolving environment/configuration problems without relying on AI. It is designed for developers who need deterministic, secure, and instant validation of their .env setups across complex codebases.
Overview
Modern development workflows frequently involve multiple environments (.env, .env.local, .env.production) and variables spread across thousands of source files. When a required variable is missing or misconfigured, it usually results in confusing runtime crashes. CSEdge Environment Doctor centralizes environment validation right inside Visual Studio Code.
The extension continuously parses your environment files and source code, presents real-time health metrics in a dedicated Activity Bar and Editor Tab dashboard, and provides direct click-to-open file redirections. It is intended for frontend developers working with tools like Vite and Next.js, backend developers running Node.js services, and full-stack developers managing multiple local configs concurrently.
Feature Highlights
- Real-time environment validation with automatic silent background scanning on save
- Native Click-to-Open redirections directly from the Dashboard to your source code
- Advanced AST parsing that intelligently ignores commented-out variables
- Cross-comparison between
.env.example templates and active .env files to catch inconsistencies
- Real-time detection of missing variables, unused variables, and malformed declarations
- Dedicated Activity Bar integration with a custom CSEdge view
- Developer-friendly dashboard interface built on native
@vscode/webview-ui-toolkit
- Live status bar integration showing your current environment health score
- Strict Privacy: Zero telemetry. No
.env contents are ever sent outside your local machine
Who This Extension Is For
- Frontend developers relying on complex
VITE_* or NEXT_PUBLIC_* variables
- Backend developers managing sensitive API keys and database credentials
- Full-stack developers coordinating configuration across several services at once
- Enterprise teams that require strict local data privacy guarantees without AI inference
Installation For Local Development
Step 1 – Clone the Repository
git clone https://github.com/durgesh-vaigandla/environment-doctor.git
cd environment-doctor
Step 2 – Install Dependencies
npm install
Step 3 – Open the Project in Visual Studio Code
Open the cloned project folder in VS Code.
Step 4 – Run the Extension in Development Mode
Press F5 in VS Code to launch an Extension Development Host window.
This opens a new VS Code window with the extension loaded in development mode, allowing you to test the Activity Bar view, commands, and real-time scanning behavior without publishing the extension.
Testing The Extension
Use the following workflow to validate the extension end to end:
- Create a
.env file with API_KEY=123 and a .env.example file with API_KEY= and DB_HOST=.
- Open a source file (e.g.
index.ts) and add console.log(process.env.MISSING_VAR);.
- Open the CSEdge Environment Doctor icon from the VS Code Activity Bar.
- Verify that the dashboard instantly reports the missing
MISSING_VAR.
- Verify that the "Inconsistencies" tab flags
DB_HOST as missing from your local .env.
- Click any highlighted file path to instantly navigate to the exact line in your editor.
- Comment out the
process.env.MISSING_VAR usage and save the file. The dashboard will instantly auto-update!
Build And Package The Extension
To generate a distributable VS Code extension package:
npm install -g @vscode/vsce
vsce package --no-dependencies
This command produces a .vsix file in the project root. That file can be used for local installation, internal distribution, or later release workflows.
Install The Extension Locally
To install the generated .vsix package in Visual Studio Code:
- Open VS Code.
- Go to the Extensions panel.
- Click the three-dot menu in the top-right corner.
- Choose Install from VSIX...
- Select the generated
.vsix file from the project directory.
After installation, the CSEdge Environment Doctor icon will appear in the Activity Bar on the left side of the editor.
Commands
CSEdge: Environment Doctor - Open Dashboard
CSEdge: Environment Doctor - Scan Workspace
Project Structure
The project is organized to keep scanning logic, process control, and UI concerns clearly separated:
src/
analysis/ Core environment variable scanning and parsing logic
config/ Configuration management for exclusion globs
detectors/ Language-specific usage detectors (JavaScript, TypeScript, etc.)
diagnostics/ VS Code Problem tab integration
models/ Shared TypeScript domain types
providers/ CodeLens and Hover providers
ui/ Webview provider, Sidebar Provider, and UI HTML generation
media/ Icons and webview styling assets
package.json Extension manifest, contribution points, scripts, metadata
README.md Repository and marketplace-facing documentation
Technical Notes
- Source parsing is done using deterministic regex analysis, not AI inference, ensuring high-speed local processing.
- The
JavascriptDetector meticulously strips // and /* */ comments before matching to prevent false positives.
- Re-scanning occurs silently on
onDidSaveTextDocument to keep the UI in real-time sync.
Maintainer
Maintained by CSEdge
Developed by Durgesh Vaigandla
Contribution Guidelines
Contributions, feedback, and improvement proposals are welcome. A dedicated contribution process can be added as the project evolves. For now, contributors should open an issue describing the proposed change before submitting substantial modifications.
License
This project is currently distributed under the terms defined in the LICENSE file.