Description
Parse the explicitly JSON-double-quoted dotenv subset only, with JSON escapes and literal dollar signs; not shell interpolation or every dotenv implementation.
Environment assignments pair names with literal string values. Repeated names need an explicit first/last policy, and missing values differ from present empty strings. A dotenv file and a shell program can use different quoting and expansion rules; these tools implement their stated literal subsets using supplied data.
Parse the explicitly JSON-double-quoted dotenv subset only, with JSON escapes and literal dollar signs; not shell interpolation or every dotenv implementation.
When to use this tool
Use this tool to parse the explicitly JSON-double-quoted dotenv subset only, with JSON escapes and literal dollar signs; not shell interpolation or every dotenv implementation.
How to use the tool and how it works
- Enter token using the input definitions below.
- Run the operation. Resolve malformed-input errors before interpreting the result.
- Read result.value. Interpret signs, units, ordering and null values using the rules below.
Require a double-quote prefix, parse the complete token as JSON and require a string result. Decode JSON escapes while leaving dollar-reference text literal.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| token | One complete quoted-value token in the operation’s supported dialect. | Text, at most 8,192 UTF-16 code units; the stated grammar and narrower limits also apply. |
| Output field | Interpretation |
|---|---|
| result | Object containing the fields below. |
| result.value | Literal decoded or parsed value string. |
{
"input": {
"token": "\"a\\nb\""
},
"output": {
"result": {
"value": "a\nb"
}
}
}Limitations and assumptions
- This accepts the JSON-double subset rather than every dotenv quoting dialect or shell expansion rule.
- Portable assignment records require names matching [A-Za-z_][A-Za-z0-9_]* and NUL-free values. Name matching is case-sensitive. Reference scanners and quoted-value helpers follow only their own stated grammar and do not read the process environment.
- Every declared top-level input is required and unknown fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
- Numeric outputs must be finite and within the absolute safe-integer magnitude; exact larger integers use decimal text. Source positions are zero-based UTF-16 offsets and span ends are exclusive unless a different convention is explicitly stated.
Alternative or Complementary methods
Select the consuming application’s dotenv dialect explicitly. Keep literal substitution separate from recursive expansion and shell execution, and retain occurrence provenance when resolving duplicate assignments.
References
Similar or alternative tools
- Restricted Dotenv Single Quoted Value Parser
Parse a restricted complete single-quoted dotenv value literally; no escape or interpolation processing, embedded single quotes and newlines reject.
- Dotenv Literal Value Quote Plan
Plan literal dotenv value spelling for this restricted unquoted-or-JSON-double dialect; quoted dollar text stays literal, no shell execution compatibility claim.