Code · Made a little simpler

Environment Variable Naming Linter

Lint dotenv assignments or standalone names against five styles and an optional required prefix. Review portable identifier findings, duplicate locations and suggested spellings.

Free to useNo account neededProcessed on your device
Your workspaceProcessed on your device

Paste .env assignments, export declarations or one variable name per line. The report includes names and locations.

Add this tool to your website

Paste this code into your page to add the tool and a visible ToolMellow credit link.

HTML embed code
Preview embed

Environment Variable Naming Linter: how to use it

  1. Paste or open a list of variable names or .env assignments. Load the names sample to see a duplicate, a reserved name and a suggestion collision.
  2. Choose a case convention and add a required prefix if your project uses one.
  3. Select Lint variable names, review the line findings and check all application references before renaming a key.

Limits and notes

Use up to 262,144 UTF-16 code units per input and up to 10,000 lines of dotenv text. Processing takes place in your browser. Reports the first 100 findings. The reserved-name list covers common shell and runtime keys. A spelling suggestion leaves source and application references for you to review.

How your privacy works →

Environment Variable Naming Linter: common questions

Can a kebab-case name pass the style check but fail the identifier check?

Yes. A name such as api-url matches kebab-case while containing a hyphen outside Node.js dotenv’s portable identifier grammar.

How are duplicates identified?

Names are compared exactly as written, including case. A duplicate points to the first occurrence.

Will the linter read names inside a quoted multiline value?

A quoted multiline assignment is scanned as one entry. Any line inside that value belongs to the surrounding assignment.

Guides