oxc-project/oxc - CodSpeed

oxc

Blog Docs Changelog

Performance History

Latest Results

feat(semantic): extend `MemberWriteTarget` to cover all property modification patterns The `MemberWriteTarget` flag (added in #20772) was only set for simple `=` assignments. This extends it to compound assignments (`+=`), update expressions (`++/--`), and `delete`, making it useful for any downstream consumer that needs to detect property-modification-only references. Changes: - `visit_member_expression`: change `is_write_only()` to `is_write()` so compound and update expressions also trigger the flag - Add `visit_unary_expression` override: set `Write` for `delete` on member expressions (not bare identifiers like `delete x` in sloppy mode) - Fix `MemberWriteTarget` leaking into conditional test positions (`(a ? x : y).foo = 1` was incorrectly marking `a`) - Update doc comments to reflect broader scope Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

feat/semantic-member-write-target

2 minutes ago

fix(allocator): remove unsafe hacks from `from_raw_parts` methods (#21283) Until recently, our `Allocator` was based on `bumpalo`. `Allocator::from_raw_parts` (which is used by raw transfer) used some horrible hacks to determine the layout of `Bump`, and to reach in to `ChunkFooter` and mutate it, despite it not being exposed by `bumpalo`. Now that we've copied `bumpalo`'s code into `oxc_allocator` crate, we can remove these hacks and work with the actual `Bump` internals. This removes a bunch of very dodgy unsafe code. There wasn't a bug to fix, per se, but the hacks used by `Allocator::from_raw_parts` were so egregious that I think we can consider removing them a fix.

main

3 minutes ago

test(allocator): skip failing test on 32-bit platforms

om/04-10-test_allocator_skip_failing_test_on_32-bit_platforms

4 minutes ago

refactor(linter): simplify `no-param-reassign` using `MemberWriteTarget` flag Replace the 97-line `is_modifying_property()` ancestor-walking function with a single `reference.flags().is_member_write_target()` check. Now that `MemberWriteTarget` covers all property modification patterns (simple `=`, compound `+=`, update `++/--`, `delete`, for-in/of, destructuring), the manual ancestor walk is no longer needed. Before: ```rust fn is_modifying_property(reference: &Reference, ctx: &LintContext) -> bool { // 97 lines walking ancestor chain matching 15+ AstKind variants } ``` After: ```rust reference.flags().is_member_write_target() ``` Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

refactor/no-param-reassign-member-write-target

5 minutes ago

docs(linter): jest/prefer-snapshot-hint: add doc comment for snapshot hint mode (#21290)

main

6 minutes ago

docs(linter): add missing docs for config options in `react` plugin (#21289)

main

7 minutes ago

feat(semantic): extend `MemberWriteTarget` to cover all property modification patterns The `MemberWriteTarget` flag (added in #20772) was only set for simple `=` assignments. This extends it to compound assignments (`+=`), update expressions (`++/--`), and `delete`, making it useful for any downstream consumer that needs to detect property-modification-only references. Changes: - `visit_member_expression`: change `is_write_only()` to `is_write()` so compound and update expressions also trigger the flag - Add `visit_unary_expression` override: set `Write` for `delete` on member expressions (not bare identifiers like `delete x` in sloppy mode) - Fix `MemberWriteTarget` leaking into conditional test positions (`(a ? x : y).foo = 1` was incorrectly marking `a`) - Update doc comments to reflect broader scope Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

feat/semantic-extend-member-write-target

7 minutes ago

docs(linter): jest/prefer-snapshot-hint: add doc comment for snapshot hint mode (#21290)

04-09-docs_linter_jest_prefer-snapshot-hint_add_doc_comment_for_snapshot_hint_mode

11 minutes ago

Latest Branches

0%

feat(semantic): extend `MemberWriteTarget` to cover all property modification patterns#21205

22 hours ago

327c2a5

feat/semantic-extend-member-write-target

0%

docs(linter): jest/prefer-snapshot-hint: add doc comment for snapshot hint mode#21290

18 minutes ago

03865fa

04-09-docs_linter_jest_prefer-snapshot-hint_add_doc_comment_for_snapshot_hint_mode

0%

docs(linter): add missing docs for config options in `react` plugin#21289

18 minutes ago

a6fe09b

04-09-docs_linter_add_missing_docs_for_config_options_in_react_plugin

© 2026 CodSpeed Technology

Home Terms Privacy Docs