Changesets currently has built-in support for formatting generated files with Prettier, but there does not appear to be a way to use oxfmt instead.
Our project uses oxfmt as the standard formatter, so Changesets-generated files end up being handled differently from the rest of the codebase. This creates extra friction in CI and local workflows, especially for teams that have fully moved away from Prettier.
It would be helpful if Changesets supported oxfmt as an alternative formatter, or more generally allowed configuring which formatter to use for generated/updated files.
Expected behavior
One of the following would solve the issue:
Native support for oxfmt, similar to the existing Prettier integration.
A configurable formatter option, for example allowing users to specify a formatter command or formatter type.
A formatter abstraction so other tools besides Prettier can be plugged in.
Why this would help
- Many projects are standardizing on
oxfmt
- Generated Changesets files should follow the same formatting rules as the rest of the repo
- It avoids requiring Prettier only for Changesets
- It reduces formatting noise in commits and CI
Example use case
A repo uses oxfmt for formatting and does not include Prettier. When Changesets creates or updates files, those files are not formatted consistently with the rest of the repository. Supporting oxfmt would make Changesets fit better into that workflow.
Additional note
If full oxfmt support is not desirable, even a generic “custom formatter” hook/configuration would be a big improvement.
Changesets currently has built-in support for formatting generated files with Prettier, but there does not appear to be a way to use oxfmt instead.
Our project uses oxfmt as the standard formatter, so Changesets-generated files end up being handled differently from the rest of the codebase. This creates extra friction in CI and local workflows, especially for teams that have fully moved away from Prettier.
It would be helpful if Changesets supported oxfmt as an alternative formatter, or more generally allowed configuring which formatter to use for generated/updated files.
Expected behavior
One of the following would solve the issue:
Native support for
oxfmt, similar to the existing Prettier integration.A configurable formatter option, for example allowing users to specify a formatter command or formatter type.
A formatter abstraction so other tools besides Prettier can be plugged in.
Why this would help
oxfmtExample use case
A repo uses oxfmt for formatting and does not include Prettier. When Changesets creates or updates files, those files are not formatted consistently with the rest of the repository. Supporting oxfmt would make Changesets fit better into that workflow.
Additional note
If full
oxfmtsupport is not desirable, even a generic “custom formatter” hook/configuration would be a big improvement.