penv for VS Code
Completions, hover docs and problems in .env.schema files for every decorator, function and filter penv knows: @sensitive, @rotate=90d, hash($API_KEY, algo=sha256, length=8). Go-to-definition and an outline are included.
All of it comes from the installed penv, served by penv lsp; the extension only starts it. Update penv (npm i -g @penvhq/cli) to get new decorators, functions and filters. Tested on VS Code 1.90 and current stable.
Requires
penv 1.0.0-beta.3 or later (install). The extension warns when your penv has no lsp command.
penv.path |
Binary started |
| empty (default) |
first penv on PATH; relative entries are skipped, and an npm i -g @penvhq/cli launcher resolves to the platform binary behind it |
| a path |
that file |
penv.path is machine-scoped: only your user settings can set it, so an untrusted workspace cannot choose the program.
Features
| Feature |
Covers |
| Diagnostics |
What penv check reports for the schema: parse errors, ignored decorators, @import targets, .penv/config.toml public prefixes and schema version, overdue @rotate keys in local mode |
| Completion |
Decorators, @type values and constraints, @rotate periods, $KEY, ${KEY \| filter}, penv(env/KEY), functions |
| Hover |
Each decorator and function, marked penv extension, @env-spec or varlock; each key's type, required, sensitive, @hosts and rotation |
| Definition |
$KEY, ${KEY}, ref(KEY), @currentEnv=$KEY |
.penv/config.toml |
Completion of sections, settings, URL parts and declared keys; hover for each setting; problems for TOML errors, unknown settings, wrong types and public entries naming an undeclared key (unchecked when the schema has @import) or a URL part penv check refuses; penv check alone checks that a [hash] entry is a hash() call |
penv lsp serves only .env.schema and .penv/config.toml, never reads .env or .env.*, and sends no network request.
Syntax highlighting
This extension adds no grammar. Install varlock's @env-spec extension (varlock.dev) for highlighting; the two run side by side.
Commands
| Command |
Does |
penv: Restart language server |
Stops and starts penv lsp |
Changing penv.path restarts the server too. Server output is in the penv output channel.
Other editors
Any LSP client can run penv lsp on stdio for files named .env.schema. Neovim 0.11:
vim.filetype.add({ filename = { [".env.schema"] = "envschema" } })
vim.lsp.config("penv", { cmd = { "penv", "lsp" }, filetypes = { "envschema" }, root_markers = { ".env.schema" } })
vim.lsp.enable("penv")
Helix 25.07, languages.toml:
[language-server.penv]
command = "penv"
args = ["lsp"]
[[language]]
name = "env-schema"
scope = "source.env-schema"
file-types = [{ glob = ".env.schema" }]
language-servers = ["penv"]
License
MIT
