Repository navigation
Description
Description
This will track the overall status of the HTML parser and formatter. This issue can be closed when the feature flag for HTML is removed, the HTML parser and formatter is publicly available, and it is enabled by default. This does not track anything for the HTML analyzer (for lint rules).
This is necessary in order for Biome to support framework specific template languages, like Vue, Svelte, and Angular. If you are a user of one of these frameworks, Biome already has support for processing embedded JS/TS in these files, but with some caveats. We have recommended configuration here to help provide the best experience for the time being.
Status
Overall: Kinda flaky, but technically functional.
- Available in the playground
- Parses all prettier formatter tests.
- Formats all prettier formatter tests.
- Support for prettier's options
- 📎 HTML: Implement "Bracket same line" option #4024
- 📎 HTML: Implement "Attribute Position" option #4828
- HTML specific
-
htmlWhitespaceSensitivity -
vueIndentScriptAndStylefeat(htmlish): implementindentScriptAndStyleoption #7333
-
- Formats embedded languages, CSS and JS in style and script tags. (see also: 📎 Embedded language formatting #3334 )
- Migrations for relevant prettier configuration to biome
How to Contribute
All well defined smaller tasks can be found by looking at the L-HTML label. Looking to contribute? Start by looking there.
Activity
TyOverby commentedon Jan 7, 2025
dyc3 commentedon Jan 7, 2025
sandstrom commentedon Jan 23, 2025
Probably something you've thought about, but HTML isn't always the 'vanilla' flavour. Handlebars, Liquid, ERB and several other templating languages exist.
They often add some 'special tags' on top of HTML.
As a first, it would be great if it could just 'ignore' those sections, i.e. continue parsing the file but not trying to interpret anything non-standard.
Then maybe as a second step also understand the handlebars/liquid/erb etc. stuff (probably via plugins?).
ematipico commentedon Jan 23, 2025
@sandstrom you might not know that, but Biome parsers are recoverable and error resilient, which means you can have even non-standard syntax inside (in this case) an HTML file, and you'll still get something somewhat analysable :)
https://biomejs.dev/playground/?lintRules=all&files.main.html=PAB1AGwAIABjAGwAYQBzAHMAPQAiAHAAZQBvAHAAbABlAF8AbABpAHMAdAAiAD4ACgAgACAAewB7ACMAZQBhAGMAaAAgAHAAZQBvAHAAbABlAH0AfQAKACAAIAAgACAAPABsAGkAPgB7AHsAdABoAGkAcwB9AH0APAAvAGwAaQA%2BAAoAIAAgAHsAewAvAGUAYQBjAGgAfQB9AAoAPAAvAHUAbAA%2BAA%3D%3D
sandstrom commentedon Jan 23, 2025
@ematipico Sounds like you've already thought about it! 😄 Great!
ismailkarsli commentedon Feb 23, 2025
Is there a chance to bring this feature as
--experimental?dyc3 commentedon Feb 23, 2025
I'm planning to have the HTML formatter in 2.0 in some form. It just won't be enabled by default most likely so that we can have users try it out and report bugs.
12 remaining items
dyc3 commentedon Dec 11, 2025
@Azarattum There's still significant bugs that prevent us from doing that.
uncenter commentedon Dec 11, 2025
Wouldn't you argue that it shouldn't be marked as Supported then?
ematipico commentedon Dec 12, 2025
Our definition of supported might differ from yours. Our definition is mostly around infrastructure and stability.
Infrastructure, we're solid. Stability, almost there. So we decided mark it as supported, but still opt-in. We highlighted this multiple times in our blog posts. Would you want to update this table too? If so how?
Also, this umbrella has nothing to do with HTML-ish languages.
Azarattum commentedon Dec 12, 2025
Putting something like "* requires manual opt-in" bellow the table and marking such languages with an asterisk, would be a great help. I, personally, often skim through this table to assess if I could use biome for a particular project.
From my point of view
🟡: Experimentalfeels like "requires opt-in, expect bugs" and✅: Supported- "production ready, enabled by default"ematipico commentedon Dec 12, 2025
That's fair. We're definitely in a weird situation so apologies if that's confusing. Would you mind sending a PR? You can click the "edit page" link at the bottom
Azarattum commentedon Dec 12, 2025
@ematipico, sure: biomejs/website#3632
BePo65 commentedon Feb 19, 2026
Perhaps the issues #8336 and #9138 should be subissues of this issue?
feat(github-issues): linked issues expand, collapse, and show type an…
feat(github-issues): linked issues expand, collapse, and show type an…
feat(github-issues): linked issues expand, collapse, and show type an…
feat(github-issues): linked issues expand, collapse, and show type an…
feat(github-issues): linked issues expand, collapse, and show type an…
feat(github-issues): linked issues expand, collapse, and show type an…
feat(github-issues): linked issues expand, collapse, and show type an…
feat(github-issues): linked issues expand, collapse, and show type an…