Visitar URL original
fix(parser): html processing instructions by ematipico · Pull Request #10702 · biomejs/biome · GitHub
Skip to content

fix(parser): html processing instructions - #10702

Merged
ematipico merged 1 commit into
mainfrom
fix/html-parser-instructions
Jun 22, 2026
Merged

ematipico merged 1 commit into
mainfrom
fix/html-parser-instructions

Conversation

@ematipico

Copy link
Copy Markdown
Member

Summary

Closes #10612

Test Plan

Added new tests

Docs

@ematipico
ematipico requested review from a team June 19, 2026 11:04
@github-actions

Copy link
Copy Markdown
Contributor

✅ Organic activity

No automation signals detected in the analyzed events.

View full analysis →

This is an automated analysis by AgentScan

@changeset-bot

changeset-bot Bot commented Jun 19, 2026 •

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 5f7d0e6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 13 packages
Name Type
@biomejs/biome Patch
@biomejs/cli-win32-x64 Patch
@biomejs/cli-win32-arm64 Patch
@biomejs/cli-darwin-x64 Patch
@biomejs/cli-darwin-arm64 Patch
@biomejs/cli-linux-x64 Patch
@biomejs/cli-linux-arm64 Patch
@biomejs/cli-linux-x64-musl Patch
@biomejs/cli-linux-arm64-musl Patch
@biomejs/wasm-web Patch
@biomejs/wasm-bundler Patch
@biomejs/wasm-nodejs Patch
@biomejs/backend-jsonrpc Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions github-actions Bot added A-Linter Area: linter A-Parser Area: parser A-Formatter Area: formatter A-Tooling Area: internal tools L-HTML Language: HTML and super languages L-Yaml Language: Yaml labels Jun 19, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Parser conformance results on

js/262

Test result main count This PR count Difference
Total 53394 53394 0
Passed 52113 52113 0
Failed 1239 1239 0
Panics 42 42 0
Coverage 97.60% 97.60% 0.00%

jsx/babel

Test result main count This PR count Difference
Total 38 38 0
Passed 37 37 0
Failed 1 1 0
Panics 0 0 0
Coverage 97.37% 97.37% 0.00%

markdown/commonmark

Test result main count This PR count Difference
Total 652 652 0
Passed 652 652 0
Failed 0 0 0
Panics 0 0 0
Coverage 100.00% 100.00% 0.00%

symbols/microsoft

Test result main count This PR count Difference
Total 5467 5467 0
Passed 1915 1915 0
Failed 3552 3552 0
Panics 0 0 0
Coverage 35.03% 35.03% 0.00%

ts/babel

Test result main count This PR count Difference
Total 658 658 0
Passed 574 574 0
Failed 84 84 0
Panics 0 0 0
Coverage 87.23% 87.23% 0.00%

ts/microsoft

Test result main count This PR count Difference
Total 18876 18876 0
Passed 13010 13010 0
Failed 5865 5865 0
Panics 1 1 0
Coverage 68.92% 68.92% 0.00%

@coderabbitai

coderabbitai Bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

The PR adds first-class support for HTML/XML processing instructions (<?...?>) throughout the Biome HTML toolchain. New PI_START and PI_END token kinds and an HTML_PROCESSING_INSTRUCTION grammar node are defined in the codegen sources. The HTML lexer is extended to emit these tokens. A new parse_processing_instruction parser function handles the <?target attrs?> structure, with a diagnostic for illegal leading spaces. The HtmlProcessingInstruction syntax node gains find_attribute_by_name and is handled in is_javascript_tag/is_style_tag. A dedicated formatter rule and generated trait impls are added. Both use_anchor_content and use_heading_content lint rules now treat processing instructions as accessible content. Parser and formatter test fixtures are included. This fixes issue #10612.

Possibly related PRs

  • biomejs/biome#9716: Implements the useHeadingContent lint rule in use_heading_content.rs, the same file where has_accessible_content is extended to handle HtmlProcessingInstruction.

Suggested labels

A-Parser, A-Formatter, L-HTML

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title 'fix(parser): html processing instructions' clearly and concisely describes the main change—adding parser support for HTML/XML processing instructions to fix issue #10612.
Description check ✅ Passed The description is related to the changeset, referencing issue #10612 and mentioning test additions, though it could be more detailed.
Linked Issues check ✅ Passed The PR fully addresses issue #10612 by implementing parser support for processing instructions, formatter support, linting updates, and test cases covering both valid and error scenarios.
Out of Scope Changes check ✅ Passed All changes are within scope—lexer updates, parser enhancements, formatter implementation, linting rule updates, and test fixtures directly support processing instruction handling.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/html-parser-instructions

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

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.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.changeset/yellow-places-dig.md:
- Line 5: The changeset file uses an incorrect format for the bugfix prefix.
Change the punctuation after the issue link from a period to a colon in the line
that starts with Fixed. The correct format should be Fixed [`#10612`](issue-link):
followed by the description, not Fixed [`#10612`](issue-link). followed by the
description. Update line 5 to follow the required bugfix changeset prefix format
with a colon separator between the issue reference and the description text.

In `@crates/biome_html_formatter/src/html/auxiliary/processing_instruction.rs`:
- Around line 24-27: The formatting logic for processing instructions
unconditionally emits space() before and after attributes.format(), which causes
unnecessary whitespace when attributes are empty (resulting in `<?target?>`
becoming `<? target ?>` with extra spaces). Conditionally emit the space() calls
only when attributes are not empty - check whether attributes contain any
content before calling space() on line 24 (before attributes.format()) and
before space() on line 26 (after attributes.format()).

In `@crates/biome_html_parser/src/syntax/mod.rs`:
- Line 245: Remove the leftover debug macro calls from the parser hot paths.
Delete the `dbg!(p.cur_text());` call at the identified location, and also
remove the similar `dbg!` call on line 504. These debug macros are not intended
for committed code and cause unnecessary output during normal parsing
operations.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 7cb1f6f8-4895-42a4-b582-3ce6ee74148b

📥 Commits

Reviewing files that changed from the base of the PR and between f719af6 and 5cfb470.

⛔ Files ignored due to path filters (10)
  • crates/biome_html_factory/src/generated/node_factory.rs is excluded by !**/generated/**, !**/generated/** and included by **
  • crates/biome_html_factory/src/generated/syntax_factory.rs is excluded by !**/generated/**, !**/generated/** and included by **
  • crates/biome_html_formatter/tests/specs/html/processing_instruction.html.snap is excluded by !**/*.snap and included by **
  • crates/biome_html_formatter/tests/specs/prettier/html/comments/bogus.html.snap is excluded by !**/*.snap and included by **
  • crates/biome_html_parser/tests/html_specs/error/processing_instruction.html.snap is excluded by !**/*.snap and included by **
  • crates/biome_html_parser/tests/html_specs/ok/processing_instruction.html.snap is excluded by !**/*.snap and included by **
  • crates/biome_html_syntax/src/generated/kind.rs is excluded by !**/generated/**, !**/generated/** and included by **
  • crates/biome_html_syntax/src/generated/macros.rs is excluded by !**/generated/**, !**/generated/** and included by **
  • crates/biome_html_syntax/src/generated/nodes.rs is excluded by !**/generated/**, !**/generated/** and included by **
  • crates/biome_html_syntax/src/generated/nodes_mut.rs is excluded by !**/generated/**, !**/generated/** and included by **
📒 Files selected for processing (18)
  • .changeset/yellow-places-dig.md
  • crates/biome_html_analyze/src/lint/a11y/use_anchor_content.rs
  • crates/biome_html_analyze/src/lint/a11y/use_heading_content.rs
  • crates/biome_html_formatter/src/generated.rs
  • crates/biome_html_formatter/src/html/any/element.rs
  • crates/biome_html_formatter/src/html/auxiliary/mod.rs
  • crates/biome_html_formatter/src/html/auxiliary/processing_instruction.rs
  • crates/biome_html_formatter/src/svelte/any/directive_initializer_clause.rs
  • crates/biome_html_formatter/tests/specs/html/processing_instruction.html
  • crates/biome_html_parser/src/lexer/mod.rs
  • crates/biome_html_parser/src/syntax/mod.rs
  • crates/biome_html_parser/src/syntax/parse_error.rs
  • crates/biome_html_parser/tests/html_specs/error/processing_instruction.html
  • crates/biome_html_parser/tests/html_specs/ok/processing_instruction.html
  • crates/biome_html_syntax/src/element_ext.rs
  • crates/biome_yaml_formatter/src/yaml/any/mapping_implicit_key.rs
  • xtask/codegen/html.ungram
  • xtask/codegen/src/html_kinds_src.rs

"@biomejs/biome": patch
---

Fixed [#10612](https://github.com/biomejs/biome/issues/10612). The Biome parser now correctly parses processing instructions. The following SVG doesn't throw errors anymore:

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.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use the required bugfix changeset prefix format.

Line 5 should use Fixed [#10612](...): ... (colon form), not a full stop after the issue link.

Suggested edit
-Fixed [`#10612`](https://github.com/biomejs/biome/issues/10612). The Biome parser now correctly parses processing instructions. The following SVG doesn't throw errors anymore:
+Fixed [`#10612`](https://github.com/biomejs/biome/issues/10612): The Biome parser now correctly parses processing instructions. The following SVG doesn't throw errors anymore:

As per coding guidelines, bug-fix changesets should start with Fixed [#NUMBER](issue link): .... Based on learnings, this exact format is required in Biome changesets.

🧰 Tools
🪛 LanguageTool

[locale-violation] ~5-~5: In British English, the spelling ‘anymore’ is sometimes considered incorrect. Did you mean “any more”?
Context: ... The following SVG doesn't throw errors anymore: ```svg <?xml version="1.0" encoding="...

(ANYMORE)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.changeset/yellow-places-dig.md at line 5, The changeset file uses an
incorrect format for the bugfix prefix. Change the punctuation after the issue
link from a period to a colon in the line that starts with Fixed. The correct
format should be Fixed [`#10612`](issue-link): followed by the description, not
Fixed [`#10612`](issue-link). followed by the description. Update line 5 to follow
the required bugfix changeset prefix format with a colon separator between the
issue reference and the description text.

Sources: Coding guidelines, Learnings

Comment on lines +24 to +27
space(),
attributes.format(),
space(),
end_token.format()

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.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Avoid unconditional spacing when PI attributes are empty.

Line 24 and Line 26 always emit spaces, so <?target?> can format with extra internal whitespace. Please gate spacing on whether attributes exist.

Suggested fix
         write!(
             f,
-            [
-                start_token.format(),
-                target.format(),
-                space(),
-                attributes.format(),
-                space(),
-                end_token.format()
-            ]
+            if attributes.is_empty() {
+                [start_token.format(), target.format(), space(), end_token.format()]
+            } else {
+                [
+                    start_token.format(),
+                    target.format(),
+                    space(),
+                    attributes.format(),
+                    space(),
+                    end_token.format()
+                ]
+            }
         )
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@crates/biome_html_formatter/src/html/auxiliary/processing_instruction.rs`
around lines 24 - 27, The formatting logic for processing instructions
unconditionally emits space() before and after attributes.format(), which causes
unnecessary whitespace when attributes are empty (resulting in `<?target?>`
becoming `<? target ?>` with extra spaces). Conditionally emit the space() calls
only when attributes are not empty - check whether attributes contain any
content before calling space() on line 24 (before attributes.format()) and
before space() on line 26 (after attributes.format()).

@codspeed

codspeed Bot commented Jun 19, 2026 •

Copy link
Copy Markdown
Contributor

Merging this PR will not alter performance

✅ 67 untouched benchmarks
⏩ 189 skipped benchmarks1


Comparing fix/html-parser-instructions (5f7d0e6) with main (c245f9d)2

Open in CodSpeed

Footnotes

  1. 189 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. ↩

  2. No successful run was found on main (f719af6) during the generation of this report, so c245f9d was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

@ematipico
ematipico force-pushed the fix/html-parser-instructions branch from 5cfb470 to 5f7d0e6 Compare June 19, 2026 11:28
@coderabbitai

coderabbitai Bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Caution

Failed to replace (edit) comment. This is likely due to insufficient permissions or the comment being deleted.

Error details
{}

@ematipico
ematipico merged commit 98823fb into main Jun 22, 2026
33 checks passed
@ematipico
ematipico deleted the fix/html-parser-instructions branch June 22, 2026 13:29
@github-actions github-actions Bot mentioned this pull request Jun 22, 2026
OIRNOIR pushed a commit to OIRNOIR/YouTube-Helper-Server that referenced this pull request Jun 30, 2026
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [@biomejs/biome](https://biomejs.dev) ([source](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome)) | imports | patch | [`2.5.0` -> `2.5.1`](https://renovatebot.com/diffs/npm/@biomejs%2fbiome/2.5.0/2.5.1) |

---

### Release Notes

<details>
<summary>biomejs/biome (@&#8203;biomejs/biome)</summary>

### [`v2.5.1`](https://github.com/biomejs/biome/blob/HEAD/packages/@&#8203;biomejs/biome/CHANGELOG.md#251)

[Compare Source](https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.0...@biomejs/biome@2.5.1)

##### Patch Changes

- [#&#8203;10722](biomejs/biome#10722) [`f8a303d`](biomejs/biome@f8a303d) Thanks [@&#8203;denbezrukov](https://github.com/denbezrukov)! - Fixed CSS formatter output for comments between import media queries.

  ```diff
  -@&#8203;import url("print.css") print,
  -/* comment */
  -screen;
  +@&#8203;import url("print.css") print, /* comment */ screen;
  ```

- [#&#8203;10738](biomejs/biome#10738) [`9fdc560`](biomejs/biome@9fdc560) Thanks [@&#8203;JamBalaya56562](https://github.com/JamBalaya56562)! - Fixed [#&#8203;9899](biomejs/biome#9899): the `json` and `json-pretty` reporters now escape backslashes in a diagnostic's `location.path`. Previously, paths containing backslashes (such as Windows-style paths) were emitted unescaped, producing invalid JSON.

  ```diff
  -    "path": "src\account\setup-passkey.tsx",
  +    "path": "src\\account\\setup-passkey.tsx",
  ```

- [#&#8203;10626](biomejs/biome#10626) [`5f837df`](biomejs/biome@5f837df) Thanks [@&#8203;tom-groves](https://github.com/tom-groves)! - Fixed [#&#8203;10625](biomejs/biome#10625): `biome migrate` no longer emits an invalid trailing comma when a renamed rule (such as `noConsoleLog` → `noConsole`) is the last member of its rule group. Previously this produced malformed output that aborted the migration of a strict-JSON `biome.json` with a parsing error.

- [#&#8203;10535](biomejs/biome#10535) [`c245f9d`](biomejs/biome@c245f9d) Thanks [@&#8203;Mokto](https://github.com/Mokto)! - Fixed a false positive in [`noUnusedVariables`](https://biomejs.dev/linter/rules/no-unused-variables/) for Svelte files where variables referenced inside `{@&#8203;html expr}` blocks were incorrectly reported as unused.

- [#&#8203;10668](biomejs/biome#10668) [`a0f197e`](biomejs/biome@a0f197e) Thanks [@&#8203;Netail](https://github.com/Netail)! - The `biome init` command has been updated to include a more up-to-date URL to [the first-party extensions page](https://biomejs.dev/editors/first-party-extensions/).

- [#&#8203;10667](biomejs/biome#10667) [`d8c3e87`](biomejs/biome@d8c3e87) Thanks [@&#8203;Netail](https://github.com/Netail)! - Fixed [#&#8203;10664](biomejs/biome#10664): [useErrorCause](https://biomejs.dev/linter/rules/use-error-cause/) now correctly detects a shorthand property.

- [#&#8203;10696](biomejs/biome#10696) [`ef2373f`](biomejs/biome@ef2373f) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed [#&#8203;9566](biomejs/biome#9566). Improved how the Biome Language Server loads multiple configuration files inside a workspace.

- [#&#8203;10705](biomejs/biome#10705) [`4ccb410`](biomejs/biome@4ccb410) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed [#&#8203;10652](biomejs/biome#10652). Biome plugins are now properly filtered when using `--only` and `--skip` flags.

- [#&#8203;10669](biomejs/biome#10669) [`aa0a6eb`](biomejs/biome@aa0a6eb) Thanks [@&#8203;Netail](https://github.com/Netail)! - Fixed [#&#8203;10651](biomejs/biome#10651): [useInlineScriptId](https://biomejs.dev/linter/rules/use-inline-script-id/) now correctly trims trivia to detect if an id attribute has been set.

- [#&#8203;10689](biomejs/biome#10689) [`844b1be`](biomejs/biome@844b1be) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed [#&#8203;10658](biomejs/biome#10658). The issue was caused by the "Go-to definition" editor feature, which was enabled by default. The feature is now **disabled by default**. To work, the feature triggers the scanner to build the module graph. This caused memory leak issues in cases where Biome starts in the home directory to modify files.

  If you relied on this new feature, you must now turn on using the \[editor settings] of the extension e.g. [Zed](https://biomejs.dev/reference/zed/#goto_definition) and [VSCode](https://biomejs.dev/reference/vscode/#biomegotodefinition).

- [#&#8203;10695](biomejs/biome#10695) [`043fbb5`](biomejs/biome@043fbb5) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed [#&#8203;10674](biomejs/biome#10674). Biome now throws an error when the field `level` is missing from a rule option.

- [#&#8203;10712](biomejs/biome#10712) [`5941df2`](biomejs/biome@5941df2) Thanks [@&#8203;Conaclos](https://github.com/Conaclos)! - Improved the diagnostic and the documentation of [`useFlatMap`](https://biomejs.dev/linter/rules/use-flat-map/).

- [#&#8203;10615](biomejs/biome#10615) [`23814f1`](biomejs/biome@23814f1) Thanks [@&#8203;qwertycxz](https://github.com/qwertycxz)! - Improved the DX the JSON schema when it's used by certain code editors like VSCode.

- [#&#8203;10688](biomejs/biome#10688) [`ec69489`](biomejs/biome@ec69489) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed a bug where the Biome Daemon did not correctly shut down when the editor was closed during an in-progress operation, especially while scanning.

- [#&#8203;10701](biomejs/biome#10701) [`6c2e0d7`](biomejs/biome@6c2e0d7) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed [#&#8203;10694](biomejs/biome#10694). The Biome Language Server no longer prints an error when the user hovers a variable imported from node\_modules.

- [#&#8203;10681](biomejs/biome#10681) [`888515b`](biomejs/biome@888515b) Thanks [@&#8203;Conaclos](https://github.com/Conaclos)! - Fixed [`useExportType`](https://biomejs.dev/linter/rules/use-export-type/) that reported useless details in some diagnostics.

- [#&#8203;10220](biomejs/biome#10220) [`3694a13`](biomejs/biome@3694a13) Thanks [@&#8203;theBGuy](https://github.com/theBGuy)! - Fixed [`useAnchorContent`](https://biomejs.dev/linter/rules/use-anchor-content/) false positive for `<a>` elements used as render prop values (e.g. `render={<a href="..." />}`), a pattern where the receiving component renders its children inside the anchor element.

- [#&#8203;10702](biomejs/biome#10702) [`98823fb`](biomejs/biome@98823fb) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed [#&#8203;10612](biomejs/biome#10612). The Biome parser now correctly parses processing instructions. The following SVG doesn't throw errors anymore:

  ```svg
  <?xml version="1.0" encoding="UTF-8" ?>

  <svg></svg>
  ```

</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - At any time (no schedule defined)
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMzQuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIzNC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Reviewed-on: https://git.oirnoir.dev/OIRNOIR/YouTube-Helper-Server/pulls/21
OIRNOIR pushed a commit to OIRNOIR/YouTube-Helper-Client that referenced this pull request Jun 30, 2026
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [@biomejs/biome](https://biomejs.dev) ([source](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome)) | imports | patch | [`2.5.0` -> `2.5.1`](https://renovatebot.com/diffs/npm/@biomejs%2fbiome/2.5.0/2.5.1) |

---

### Release Notes

<details>
<summary>biomejs/biome (@&#8203;biomejs/biome)</summary>

### [`v2.5.1`](https://github.com/biomejs/biome/blob/HEAD/packages/@&#8203;biomejs/biome/CHANGELOG.md#251)

[Compare Source](https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.0...@biomejs/biome@2.5.1)

##### Patch Changes

- [#&#8203;10722](biomejs/biome#10722) [`f8a303d`](biomejs/biome@f8a303d) Thanks [@&#8203;denbezrukov](https://github.com/denbezrukov)! - Fixed CSS formatter output for comments between import media queries.

  ```diff
  -@&#8203;import url("print.css") print,
  -/* comment */
  -screen;
  +@&#8203;import url("print.css") print, /* comment */ screen;
  ```

- [#&#8203;10738](biomejs/biome#10738) [`9fdc560`](biomejs/biome@9fdc560) Thanks [@&#8203;JamBalaya56562](https://github.com/JamBalaya56562)! - Fixed [#&#8203;9899](biomejs/biome#9899): the `json` and `json-pretty` reporters now escape backslashes in a diagnostic's `location.path`. Previously, paths containing backslashes (such as Windows-style paths) were emitted unescaped, producing invalid JSON.

  ```diff
  -    "path": "src\account\setup-passkey.tsx",
  +    "path": "src\\account\\setup-passkey.tsx",
  ```

- [#&#8203;10626](biomejs/biome#10626) [`5f837df`](biomejs/biome@5f837df) Thanks [@&#8203;tom-groves](https://github.com/tom-groves)! - Fixed [#&#8203;10625](biomejs/biome#10625): `biome migrate` no longer emits an invalid trailing comma when a renamed rule (such as `noConsoleLog` → `noConsole`) is the last member of its rule group. Previously this produced malformed output that aborted the migration of a strict-JSON `biome.json` with a parsing error.

- [#&#8203;10535](biomejs/biome#10535) [`c245f9d`](biomejs/biome@c245f9d) Thanks [@&#8203;Mokto](https://github.com/Mokto)! - Fixed a false positive in [`noUnusedVariables`](https://biomejs.dev/linter/rules/no-unused-variables/) for Svelte files where variables referenced inside `{@&#8203;html expr}` blocks were incorrectly reported as unused.

- [#&#8203;10668](biomejs/biome#10668) [`a0f197e`](biomejs/biome@a0f197e) Thanks [@&#8203;Netail](https://github.com/Netail)! - The `biome init` command has been updated to include a more up-to-date URL to [the first-party extensions page](https://biomejs.dev/editors/first-party-extensions/).

- [#&#8203;10667](biomejs/biome#10667) [`d8c3e87`](biomejs/biome@d8c3e87) Thanks [@&#8203;Netail](https://github.com/Netail)! - Fixed [#&#8203;10664](biomejs/biome#10664): [useErrorCause](https://biomejs.dev/linter/rules/use-error-cause/) now correctly detects a shorthand property.

- [#&#8203;10696](biomejs/biome#10696) [`ef2373f`](biomejs/biome@ef2373f) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed [#&#8203;9566](biomejs/biome#9566). Improved how the Biome Language Server loads multiple configuration files inside a workspace.

- [#&#8203;10705](biomejs/biome#10705) [`4ccb410`](biomejs/biome@4ccb410) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed [#&#8203;10652](biomejs/biome#10652). Biome plugins are now properly filtered when using `--only` and `--skip` flags.

- [#&#8203;10669](biomejs/biome#10669) [`aa0a6eb`](biomejs/biome@aa0a6eb) Thanks [@&#8203;Netail](https://github.com/Netail)! - Fixed [#&#8203;10651](biomejs/biome#10651): [useInlineScriptId](https://biomejs.dev/linter/rules/use-inline-script-id/) now correctly trims trivia to detect if an id attribute has been set.

- [#&#8203;10689](biomejs/biome#10689) [`844b1be`](biomejs/biome@844b1be) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed [#&#8203;10658](biomejs/biome#10658). The issue was caused by the "Go-to definition" editor feature, which was enabled by default. The feature is now **disabled by default**. To work, the feature triggers the scanner to build the module graph. This caused memory leak issues in cases where Biome starts in the home directory to modify files.

  If you relied on this new feature, you must now turn on using the \[editor settings] of the extension e.g. [Zed](https://biomejs.dev/reference/zed/#goto_definition) and [VSCode](https://biomejs.dev/reference/vscode/#biomegotodefinition).

- [#&#8203;10695](biomejs/biome#10695) [`043fbb5`](biomejs/biome@043fbb5) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed [#&#8203;10674](biomejs/biome#10674). Biome now throws an error when the field `level` is missing from a rule option.

- [#&#8203;10712](biomejs/biome#10712) [`5941df2`](biomejs/biome@5941df2) Thanks [@&#8203;Conaclos](https://github.com/Conaclos)! - Improved the diagnostic and the documentation of [`useFlatMap`](https://biomejs.dev/linter/rules/use-flat-map/).

- [#&#8203;10615](biomejs/biome#10615) [`23814f1`](biomejs/biome@23814f1) Thanks [@&#8203;qwertycxz](https://github.com/qwertycxz)! - Improved the DX the JSON schema when it's used by certain code editors like VSCode.

- [#&#8203;10688](biomejs/biome#10688) [`ec69489`](biomejs/biome@ec69489) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed a bug where the Biome Daemon did not correctly shut down when the editor was closed during an in-progress operation, especially while scanning.

- [#&#8203;10701](biomejs/biome#10701) [`6c2e0d7`](biomejs/biome@6c2e0d7) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed [#&#8203;10694](biomejs/biome#10694). The Biome Language Server no longer prints an error when the user hovers a variable imported from node\_modules.

- [#&#8203;10681](biomejs/biome#10681) [`888515b`](biomejs/biome@888515b) Thanks [@&#8203;Conaclos](https://github.com/Conaclos)! - Fixed [`useExportType`](https://biomejs.dev/linter/rules/use-export-type/) that reported useless details in some diagnostics.

- [#&#8203;10220](biomejs/biome#10220) [`3694a13`](biomejs/biome@3694a13) Thanks [@&#8203;theBGuy](https://github.com/theBGuy)! - Fixed [`useAnchorContent`](https://biomejs.dev/linter/rules/use-anchor-content/) false positive for `<a>` elements used as render prop values (e.g. `render={<a href="..." />}`), a pattern where the receiving component renders its children inside the anchor element.

- [#&#8203;10702](biomejs/biome#10702) [`98823fb`](biomejs/biome@98823fb) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed [#&#8203;10612](biomejs/biome#10612). The Biome parser now correctly parses processing instructions. The following SVG doesn't throw errors anymore:

  ```svg
  <?xml version="1.0" encoding="UTF-8" ?>

  <svg></svg>
  ```

</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - At any time (no schedule defined)
- Automerge
  - At any time (no schedule defined)

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4yMzQuMCIsInVwZGF0ZWRJblZlciI6IjQzLjIzNC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Reviewed-on: https://git.oirnoir.dev/OIRNOIR/YouTube-Helper-Client/pulls/8
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-Formatter Area: formatter A-Linter Area: linter A-Parser Area: parser A-Tooling Area: internal tools L-HTML Language: HTML and super languages L-Yaml Language: Yaml

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🐛 HTML parser doesn't parse <? ?> syntax

1 participant