Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@biomejs/[email protected]
Patch Changes
#7840
72afdfaThanks @ematipico! - Fixed #7838, which caused the new--css-parse-*arguments not being recognised by thecicommand.#7789
d5b416eThanks @fronterior! - Fixed the LSP methodworkspace/didChangeWorkspaceFoldersto perform incremental updates instead of replacing the entire folder list.#7852
bd254c7Thanks @dyc3! - Fixed 🐛 @theme At-Rule with Tailwind CSS internal variable (--*: initial;) causes multiple CSS parser errors #7843: The CSS parser, whentailwindDirectivesis enabled, correctly parses--*: initial;.#7872
0fe13feThanks @dyc3! - Fixed #7861: The HTML parser will now accept Svelte attribute shorthand syntax in.sveltefiles.#7866
7b2600bThanks @dyc3! - Fixed #7860: The css parser, withtailwindDirectivesenabled, will now accept@pluginoptions.#7853
fe90c78Thanks @dyc3! - Fixed 🐛 Tailwind path ignore syntax causes a parsing error #7848: The css parser withtailwindDirectivesenabled will now correctly parse tailwind's source exclude syntax:@source not "foo.css";#7878
c9f7fe5Thanks @ematipico! - Fixed #7857: Biome now parses<script>tags as TypeScript when analysing.astrofiles.#7867
b42b718Thanks @smorimoto! - Fixed incorrect option name in HTML parser error message.The error message for disabled text expressions incorrectly referred
to the
html.parser.textExpressionoption, which does not exist.Updated it to reference the correct
html.parser.interpolationoption.@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]
@biomejs/[email protected]