Parsers, not regular expressions
Indentation, quotes, flow collections, block scalars, anchors, tables and dotted keys are read properly, not matched line by line. A quoted colon stays inside the string where it belongs.
Pikkola YAML Studio, tool No. 31
Paste a YAML file, a JSON response, a TOML config or an .env line and read it back as any of the other three. The parser runs on this page, so nothing is uploaded. When something is wrong, the error names the line, the column and the character it stumbled on.
# compose.yaml services: web: image: nginx:1.27 ports: - "8080:80" environment: TZ: Asia/Seoul DEBUG: false
{
"services": {
"web": {
"image": "nginx:1.27",
"ports": ["8080:80"],
"environment": {
"TZ": "Asia/Seoul",
"DEBUG": false
}
}
}
}
The studio
One editor on the left, one answer on the right. Change the source format or the target format and the same text is read again.
There is no output yet. Paste something on the left, or load one of the examples.
No request, no account, no storage. The text and the converted result live in this page until you close it.
Each format has its own parser and its own writer. Between them sits one small data model, which is why nesting and types survive a trip from YAML to TOML.
Indentation, quotes, flow collections, block scalars, anchors, tables and dotted keys are read properly, not matched line by line. A quoted colon stays inside the string where it belongs.
Line and column come from the parser position, so a tab used for indentation or a quote left open is marked where it starts, not where the file ends.
No request, no account, no storage. The text lives in this tab and is gone when you close it. Load the page once and it works with the network off.
The parser reports what stops it and what will surprise you later. Every finding names a line and a column, and the line in the editor is marked when you click it.
Syntax first, structure second. Nothing is checked against a schema or a Compose version.
No. There is no endpoint to send it to. The four parsers and the four writers are JavaScript files on this domain, and the Content-Security-Policy allows no script or connection beyond them. Load the page once and it keeps working with the network off.
They are read and then dropped when the target format is JSON, which has no comment syntax. YAML, TOML and .env comments are also dropped, because the converter rebuilds the document from values rather than editing the text.
Almost. .env is a flat list of KEY=VALUE lines, so an object is flattened and the path is joined with an underscore and uppercased: database.host becomes DATABASE_HOST. An array of simple values is joined with commas, and an array of objects becomes one JSON string. The output panel names both cases when they happen.
TOML has no null, so a null value is left out and a warning names the key. Inside an array it becomes an empty string, because dropping it would move the other items.
It checks syntax and the structure of each format. It does not know which keys Docker Compose or Wrangler expect, so a clean result means the file is well formed, not that the service will accept it.
Block and flow style, quoted keys, single and double quoted strings, literal and folded block scalars, anchors and aliases, comments and a single document. Merge keys (<<) and custom tags are not interpreted. A file with two documents is reported rather than merged.