Plenty of semantic-release and standard-version setups keep their config in JavaScript (release.config.js) or YAML (.releaserc.yaml) rather than JSON. ferrflow migrate used to read JSON only and told you to convert the rest by hand first.

Now it reads them directly. A JavaScript config is evaluated with node. It imports the config, resolves it if it's a function, and reads the result: the same way FerrFlow already runs your ferrflow.js config, run locally against your own repo. A YAML config is parsed straight through. Both then feed the existing converters, so the mapping and the mapped/ignored/review report are identical to the JSON path.

ferrflow migrate            # auto-detects .releaserc.js, .releaserc.yaml, release.config.js, …

JavaScript configs need Node.js on your PATH; if it's missing, the error says so.