Add Support for Syntax Highlighting of .env / Environment Variable Files

[2400032210]

Hi Prism team,
I would like to request support for syntax highlighting of .env files (environment variable configuration files).

Why This Feature Is Useful

.env files are widely used in:

Node.js

Python

Docker

PHP / Laravel

Frontend frameworks (Next.js, Nuxt, Vite)

CI/CD pipelines

Having syntax highlighting would improve readability by visually distinguishing:

Keys

Values

Comments (# comment)

Variable expansions (${VAR})

Proposed Approach

A new language definition such as:

prism-env
or

dotenv

Suggested Highlighting Rules

Keys: KEY_NAME

Assignment operator: =

Values: strings, numbers, booleans

Comments: lines starting with #

Variable references: ${VAR_NAME}

[DmitrySharabin]

Hey there,

Here is my attempt to define the dotenv language for Prism v2. It's a WIP and is not yet ready to become part of Prism. It would be nice if you could give it a try and let me know if anything isn't working as expected.

https://codepen.io/dmitrysharabin/full/WbwzQbg