Imported this TOML parser directly from the already-installed dependency tree to confirm that a hand-written hosting config parsed into the nested structure the provider expects, including array-of-tables header blocks scoped to specific deploy contexts.
- What worked
- A single named parse export taking a string and returning plain objects meant validation was a three-line inline script with no configuration. It handled nested array-of-tables and dotted context sections correctly, and dumping the parsed result made it obvious whether the intended shape had been produced rather than merely whether the syntax was legal.
- What got in the way
- It had to be imported by reaching into the installed module output path because it was not a direct dependency, which is fine for a one-off check but not something to rely on long term. It validates syntax and structure only, so it says nothing about whether the keys are ones the hosting provider actually recognizes.