fix(linter/plugins): include hashbang in comments

[overlookmotel]

ESLint represents hashbangs as comments. If file has a hashbang, add it to start of comments array with type Shebang.

This fixes a handful of conformance tests.

[overlookmotel]

• fix(linter/plugins): include hashbang in comments #17231 👈 (View in Graphite)
• fix(ast_tools): visit nested objects to add __proto__: NodeProto in raw transfer codegen #17230
• feat(linter/plugins): implement code path analysis (CFG) #17229
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

CodSpeed Performance Report

Merging #17231 will not alter performance

_{Comparing om/12-21-fix_linter_plugins_include_hashbang_in_comments (cf3f489) with main (b8e321c)¹}

Summary

✅ 42 untouched
⏩ 3 skipped²

Footnotes

1. No successful run was found on om/12-21-fix_ast_tools_visit_nested_objects_to_add___proto___nodeproto_in_raw_transfer_codegen (be97ee1) during the generation of this report, so main (b8e321c) was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 3 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[Copilot]

Pull request overview

This PR enhances ESLint compatibility by representing hashbangs as comments in the AST. When a file contains a hashbang, it is now added to the start of the comments array with type Shebang, matching ESLint's behavior.

• Adds hashbang as a Shebang comment type in the comments array
• Updates TypeScript types to include "Shebang" as a valid comment type
• Fixes conformance tests for lines-around-comment, lines-around-directive, and no-trailing-spaces rules

Reviewed changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
crates/oxc_ast/src/serialize/mod.rs	Template code to prepend hashbang as Shebang comment when deserializing comments
apps/oxlint/src-js/generated/deserialize.js	Generated JavaScript deserializer with hashbang-to-comment logic
apps/oxlint/src-js/plugins/types.ts	TypeScript type update to include "Shebang" as valid Comment type
apps/oxlint/test/fixtures/comments/files/hashbang.js	New test file with hashbang to verify comment handling
apps/oxlint/test/fixtures/comments/output.snap.md	Updated test snapshots showing hashbang correctly appears as Shebang comment
apps/oxlint/conformance/snapshot.md	Conformance test results showing 3 rules now fully passing and 10 more tests passing overall

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[overlookmotel]

Merge activity

• Dec 21, 8:53 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Dec 21, 8:53 PM UTC: overlookmotel added this pull request to the Graphite merge queue.
• Dec 21, 9:01 PM UTC: Merged by the Graphite merge queue.