fix(parse/html): don't lex "use" as USE_KW when in html text content

[dyc3]

Summary

Previously, the HTML lexer emitted keyword tokens (e.g. USE_KW, STYLE_KW) when those words appear as plain text content between HTML tags. The parser has a guard (is_at_svelte_keyword) that re-lexes keyword tokens as HtmlText when they appear in a text-content position, but T![use] and T![style] were missing from that guard.

planned by sonnet 4.6 and tests generated by kimi k2.5

Test Plan

added snapshot tests

Docs

[changeset-bot]

🦋 Changeset detected

Latest commit: 0cabd62

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

[dyc3]

• chore(html): more html benchmarks #8153
• fix(parse/html): don't lex "use" as USE_KW when in html text content #9151 👈 (View in Graphite)
• refactor(parse/html): use token_set! instead of matches! for svelte keywords and directives helpers #9148
• fix(parse/html): don't lex square brackets as special tokens in contexts where they don't mean anything #9150
• main

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

[ematipico]

I would rename this, because now it doesn't contain all Svelte keywords

[dyc3]

It does because of the .union

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

Walkthrough

This patch fixes incorrect parsing of Svelte directive keywords when they appear as plain text content in HTML/Svelte files. The change modifies the SVELTE\_KEYWORDS constant to include directive keywords (use, style, bind, transition, in, out, class, animate) via union with SVELTE\_DIRECTIVE\_KEYWORDS. This ensures plain text like "use JavaScript" is correctly treated as text content rather than triggering directive parsing. Test files verify the fix handles keyword directives rendered as text within span and paragraph elements.

Possibly related PRs

• refactor(parse/html): use token_set! instead of matches! for svelte keywords and directives helpers #9148: Directly modifies the same SVELTE\_KEYWORDS constant and keyword handling logic that this PR refactors.
• fix(html): parse keywords #8569: Addresses related keyword parsing and rewind logic in the HTML/Svelte parser, including keyword-as-text detection.

Suggested reviewers

• ematipico
• chansuke

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the core change: fixing the lexing of 'use' as a keyword when appearing in HTML text content rather than as a Svelte directive.
Description check	✅ Passed	The description clearly explains the problem (missing keywords in the is_at_svelte_keyword guard), the motivation (preventing incorrect keyword token emission in text content), and includes test coverage details.

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

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dyc3/fix-use-keyword-in-html-content

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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

[codspeed-hq]

Merging this PR will not alter performance

✅ 4 untouched benchmarks
⏩ 152 skipped benchmarks¹

---

_{Comparing dyc3/fix-use-keyword-in-html-content (0cabd62) with main (4317572)}

Footnotes

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

[dyc3]

Merge activity

• Feb 20, 1:16 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Feb 20, 1:16 PM UTC: @dyc3 merged this pull request with Graphite.