Skip to content

registry: add oxfmt #8316

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jdx merged 1 commit into from
Feb 23, 2026
Merged

registry: add oxfmt #8316

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions registry/oxfmt.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
backends = ["npm:oxfmt"]

@gemini-code-assist gemini-code-assist Bot Feb 23, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Using the npm backend for a native tool like oxfmt introduces a dependency on Node.js, which is not ideal. The project's own documentation prioritizes aqua or github backends for pre-compiled binaries to avoid such unnecessary dependencies.

The oxc project's release versioning is complex, which likely prompted this choice. However, could you explore if mise's github backend can be configured to handle this case? If it's not feasible, using npm is a pragmatic workaround, but it would be good to document this trade-off with a comment in the file for future maintainers.

description = "This is the formatter for oxc."
test = { cmd = "oxfmt --version", expected = "Version: {{version}}" }
Loading