Oxfmt best practices

Use when formatting code with Oxfmt, configuring .oxfmtrc.json, or migrating formatting workflows from Prettier.

Mental model

• Treat Oxfmt as a fast formatter that aims for Prettier compatibility, not as a formatter that should be hand-tuned on every line.
• Prefer formatter-driven consistency over manual style debates.
• Keep formatting policy centralized so editor, local CLI, and CI produce the same output.

Setup and config

• Commit formatter config and shared scripts such as fmt and fmt:check.
• Use check mode in CI to verify formatting without mutating files during the build.
• Keep ignored files limited to generated output, vendored assets, or paths the formatter should not own.

Vite+ exception