migrate-oxfmt

To migrate Prettier config to Oxfmt, run a migration tool that reads your existing settings and writes a mapped .oxfmtrc.json file. You need to review the generated configuration and manually convert any unsupported overrides before committing.

Yes, you can migrate Biome formatter settings to an Oxfmt configuration file. The migration process reads your Biome config, maps common formatter options like printWidth and semi, and outputs a .oxfmtrc.json file for your JavaScript or TypeScript codebase.

When switching to Oxfmt, update your CI checks to use oxfmt --check and reconcile your editor and LSP settings. The migration process flags unsupported nested configs so you can manually adjust your automated formatting pipeline.

During an Oxfmt migration, common formatter options like printWidth, tabWidth, useTabs, semi, and singleQuote are automatically mapped. It also migrates Tailwind and package.json sorting options when detected in your original Prettier or Biome configuration.

The limitations of migrating to Oxfmt include unsupported or non-migratable overrides and nested configs that require manual conversion. You must review the generated .oxfmtrc.json before committing and enforcing it via CI to ensure accurate formatting.

Yes, the Oxfmt migration tool supports monorepos by migrating Tailwind and package.json sorting options when detected. It provides a stepwise path to convert configurations, update CI checks, and reconcile editor settings across your JavaScript or TypeScript packages.