How to migrate json config files to yaml
- Step 1Copy the JSON configuration file — Open the JSON config file in your editor and copy its full contents — tsconfig.json, .eslintrc.json, babel.config.json, or your application's config.json.
- Step 2Convert to YAML — Paste the JSON and click Convert. The output is standard YAML with 2-space indentation, unquoted string keys, and proper sequence formatting for arrays.
- Step 3Add comments where needed — Paste the YAML into your editor and add # comment lines above complex sections to explain intent. This is the primary benefit of migrating from JSON — comments are impossible in standard JSON config files.
- Step 4Rename the config file and test — Rename the config file from .eslintrc.json to .eslintrc.yaml (or .eslintrc.yml), delete the old JSON file, and run the tool (eslint ., tsc --noEmit, etc.) to verify it reads the YAML file correctly.
Frequently asked questions
Are there tools that do not support YAML config files?+
Most modern tools support both JSON and YAML. Notable exceptions include package.json (Node.js only ever reads JSON) and tsconfig.json (TypeScript does not natively support YAML, though tools like ts-node can be configured to read YAML tsconfig variants). Check your tool's documentation before migrating.
Will special characters in string values require quoting in YAML?+
YAML requires quoting for strings that start with special characters (#, :, {, [, etc.) or that contain colons followed by spaces. The converter adds quotes automatically where needed so the YAML is valid. Review quoted values after conversion to ensure nothing was missed.
Is the configuration file content sent to JAD Apps?+
No. Conversion runs entirely in your browser using js-yaml. Configuration file contents — including internal paths, package names, and rule settings — are never transmitted to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.