oxc-project/oxc - CodSpeed

oxc

Blog Docs Changelog

Performance History

Latest Results

[autofix.ci] apply automated fixes

taearls:13991/improve-conformance-runner

10 minutes ago

fix lint warning

taearls:13991/improve-conformance-runner

18 minutes ago

[autofix.ci] apply automated fixes

taearls:13991/improve-conformance-runner

25 minutes ago

merge in changes from rebase

taearls:13991/improve-conformance-runner

53 minutes ago

draft(oxlnt/lsp): support `jsPlugins`

11-18-draft_oxlnt_lsp_support_jsplugins_

1 hour ago

draft(oxlnt/lsp): support `jsPlugins`

11-18-draft_oxlnt_lsp_support_jsplugins_

1 hour ago

fix(minifier): avoid generating invalid spans (#15778) This debug assertion failed https://github.com/oxc-project/oxc/blob/ef4cc33b5cedde82d5b5f91355d7b39436bdbcd6/crates/oxc_span/src/span.rs#L169 when it's called by https://github.com/oxc-project/oxc/blob/c023ba67e07283bad3a43ef9bcc0336c94aa42ae/crates/oxc_codegen/src/gen.rs#L2123 which was caused by https://github.com/oxc-project/oxc/blob/102365da3dd02f5cdd444eaf04f8bbf91c814886/crates/oxc_minifier/src/peephole/fold_constants.rs#L445 This PR fixes these kinds of issues. This PR adds a test but does not fail even without the change. I'll fail once #15787 is done.

main

4 hours ago

feat(span): add `Span::merge_within` method (#15869) Add `Span::merge_within` method that creates a connected Span that is covered by both Spans if they are within a specified Span. The bug described in the OP of #15778 is caused by trying to create a Span assuming that the Spans are adjacent. This method would avoid that kind of issue.

main

4 hours ago

Active Branches

refactor(coverage): optimize conformance runner infrastructure

last run

10 minutes ago

0%

feat(oxlint/lsp): support `jsPlugins`

last run

1 hour ago

0%

feat(formatter/sort-imports): Support `options.groups`

last run

10 hours ago

0%

© 2025 CodSpeed Technology

Home Terms Privacy Docs