That's written in our announcement biomejs.dev/blog/biome-v...

> there are cases and framework-specific syntaxes that may not yet be fully supported (for example Svelte control-flow syntax, or Astro JSX-like syntax)

What could have we done better?

Hard to say without an issue to track it.

What went wrong? Please give us constructive criticism

Biome can fully analyse the file, apply consistent formatting and linting. That's full support, from this point of view. Both sides of the same coin.

The WASM bindings are assist-ready. The JavaScript library should be updated, so contributions are welcome!

Thanks to our Platinum Sponsor @vercel.com , which sponsored the type inference work. Thanks to depot for providing fast GitHub Action runners, as well as our other sponsors and all the Biome contributors!

In upcoming releases, we will introduce more type-aware lint rules, such as noMisusedPromises, and work on supporting HTML-like languages, embedding formatting, and additional features.

With lint domains, you can opt in lint rules based on your project needs. Since the last beta, we have introduced a domain called 'project', which enables project- and type-aware lint rules.

biomejs.dev/linter/domai...

The new, revamped, configurable import sorting is stable and packed with many features. It's a state-of-the-art feature that allows you to control packages, aliases, blank lines, copyright comments, and more! Ready to study? 👩‍🎓 Check the documentation

biomejs.dev/assist/actio...

One of the most wanted features was better monorepo management. In v2, monorepos became first-class citizens, and your packages can extend from the root configuration with a new micro-syntax. Check our guide to learn more:

biomejs.dev/guides/big-p...

Does your organisation have particular use cases? Now you can create your custom lint rules with plugins using GritQL.

biomejs.dev/linter/plugi...