chore(deps): update all non-major dependencies #3678
Merged
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 contains the following updates:
2.2.6->2.3.11.20.1->1.20.23.13.0->3.14.03.13.0->3.14.02.47.2->2.48.01.23.7->1.23.81.3.0->1.3.124.8.1->24.9.15.0.4->5.1.01.3.28->1.3.3220.0.7->20.0.80.546.0->0.548.00.546.0->0.548.00.546.0->0.548.00.546.0->0.548.04.1.3->4.2.03.13.0->3.14.05.41.3->5.42.25.8.0->5.9.048.4.1->48.6.02.11.9->2.11.103.1.1->3.1.2Release Notes
biomejs/biome (@biomejs/biome)
v2.3.1Compare Source
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 #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 #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.v2.3.0Compare Source
Minor Changes
a3e3369Thanks @arendjr! - Biome's resolver now supportsbaseUrlif specified intsconfig.json.Example
Given the following file structure:
tsconfig.json{ "compilerOptions": { "baseUrl": "./src" } }src/foo.tsIn this scenario,
import { foo } from "foo";should work regardless of thelocation of the file containing the
importstatement.Fixes #6432.
#7745
6fcbc07Thanks @dyc3! - Addedignoreoption tonoUnknownAtRules. If an unknown at-rule matches any of the items provided inignore, a diagnostic won't be emitted.#7753
63cb7ffThanks @ematipico! - Enhanced theinitcommand. Theinitcommand now checks if the existing project contains known ignore files and known generated folders.If Biome finds
.gitignoreor.ignorefiles, it will add the following configuration tobiome.json:{ + "vcs": { + "enabled": true, + "clientKind": "git", + "useIgnoreFile": true + } }If Biome finds a
dist/folder, it will exclude it automatically using the double-exclude syntax:{ + "files": { + "includes": ["**", "!!**/dist"] + } }#7548
85d3a3aThanks @siketyan! - The rules in a domain are no longer enabled automatically by the installed dependencies unless the rule is recommended.#7723
d3aac63Thanks @ematipico! - Added--css-parse-css-modulesCLI flag to control whether CSS Modules syntax is enabled.You can now enable or disable CSS Modules parsing directly from the command line:
#7723
d3aac63Thanks @ematipico! - Added--css-parse-tailwind-directivesCLI flag to control whether Tailwind CSS 4.0 directives and functions are enabled.You can now enable or disable Tailwind CSS 4.0 directive parsing directly from the command line:
#7330
272632fThanks @ematipico! - Updated the formatting of.svelteand.vuefiles. Now the indentation of the JavaScript blocks matches Prettier's:#7333
de0d2d6Thanks @dyc3! - Implemented theindentScriptAndStyleoption for vue and svelte files, with the default set tofalseto match Prettier'svueIndentScriptAndStyleoption. When enabled, this option indents the content within<script>and<style>tags to align with the surrounding HTML structure.It can be enabled with this configuration:
{ "html": { "formatter": { "indentScriptAndStyle": true } } }Which will format this code to:
#7359
ebbddc4Thanks @arendjr! - Deprecated the optionfiles.experimentalScannerIgnoresin favour of force-ignore syntax infiles.includes.files.includessupports ignoring files by prefixing globs with an exclamation mark (!). With this change, it also supports force-ignoring globs by prefixing them with a double exclamation mark (!!).The effect of force-ignoring is that the scanner will not index files matching the glob, even in project mode, even if those files are imported by other files, and even if they are files that receive special treatment by Biome, such as nested
biome.jsonfiles.Example
Let's take the following configuration:
{ "files": { "includes": [ "**", "!**/generated", "!!**/dist", "fixtures/example/dist/*.js" ] }, "linter": { "domains": { "project": "all" } } }This configuration achieves the following:
generatedfolder are not processed by the linter, but they will get indexed if a file outside ageneratedfolder imports them.distfolder are never indexed nor processed, not even if they are imported for any purpose, except:distfolder is insidefixtures/example/, its.jsfiles do get both indexed and processed.In general, we now recommend using the force-ignore syntax for any folders that contain output files, such as
build/anddist/. For such folders, it is highly unlikely that indexing has any useful benefits. For folders containing generated files, you may wish to use the regular ignore syntax so that type information can still be extracted from the files.experimentalScannerIgnoreswill continue to work for now, but you'll see a deprecation warning if you still use it.Run the
biome migrate --writecommand to automatically update the configuration file.#7698
3b6f5e3Thanks @ematipico! - Added a new reporter namedrdjson. This reporter prints diagnostics following the RDJSON format:The following command:
Will emit diagnostics in the following format:
{ "source": { "name": "Biome", "url": "https://biomejs.dev" }, "diagnostics": [ { "code": { "url": "https://biomejs.dev/linter/rules/no-unused-imports", "value": "lint/correctness/noUnusedImports" }, "location": { "path": "index.ts", "range": { "end": { "column": 11, "line": 0 }, "start": { "column": 7, "line": 0 } } }, "message": "This import is unused." }, { "code": { "url": "https://biomejs.dev/linter/rules/no-unused-imports", "value": "lint/correctness/noUnusedImports" }, "location": { "path": "index.ts", "range": { "end": { "column": 10, "line": 1 }, "start": { "column": 9, "line": 1 } } }, "message": "Several of these imports are unused." } ] }#7719
188a767Thanks @cadunass! - TheformatWithErrorsoption can now be set via CLI using the--format-with-errorsflag.This flag was previously only available in the configuration file. It allows formatting to proceed on files with syntax errors, which is useful during development when you want to auto-format code while fixing syntax issues.
Example
#7723
d3aac63Thanks @ematipico! - Added--json-parse-allow-commentsCLI flag to control whether comments are allowed in JSON files.You can now enable or disable comment parsing in JSON files directly from the command line:
#7723
d3aac63Thanks @ematipico! - Added--json-parse-allow-trailing-commasCLI flag to control whether trailing commas are allowed in JSON files.You can now enable or disable trailing comma parsing in JSON files directly from the command line:
#7758
cea002fThanks @ematipico! - Promoted new lint rules:noNonNullAssertedOptionalChainto the suspicious groupuseReactFunctionComponentsto thestylegroupuseImageSizeto thecorrectnessgroupuseConsistentTypeDefinitionsto thestylegroupuseQwikClasslistto thecorrectnessgroupnoSecretsto thesecuritygroupRemoved the lint rule
useAnchorHref, because its use case is covered byuseValidAnchor.#6356
296627dThanks @wrick17! - Added the newcheckstylereporter. When--reporter=checkstyleis passed to the CLI, Biome will emit diagnostics for Checkstyle format:#7488
b13e524Thanks @kpapa05! - Added "@rbxts/react" as an alias for "react" for handling the reactClassic jsxRuntime.#7536
0bccd34Thanks @TheAlexLichter! - Added.oxlintrc.jsonto well-known files.#7548
85d3a3aThanks @siketyan! - The following rules are now a part of thereactdomain, and they won't be enabled automatically unless you enabled the domain, or Biome detectsreactas a dependency of your closestpackage.json:lint/correctness/noChildrenProp(recommended)lint/correctness/noReactPropAssignmentslint/security/noDangerouslySetInnerHtml(recommended)lint/security/noDangerouslySetInnerHtmlWithChildren(recommended)lint/style/useComponentExportOnlyModuleslint/suspicious/noArrayIndexKey(recommended)#7667
480909aThanks @ematipico! - Added the ability to show severityInformationdiagnostics in reporter outputs.If one or more rules are triggered, and they are configured to emit an
Informationdiagnostic, now they're counted in the final output:#7702
28e8860Thanks @ematipico! - Added linting and assist support for.htmlfiles, with addition of two new configurations:html.linter.enabledhtml.assist.enabledThe HTML linter, in this release, only contains the rule
noHeaderScope. More rules will be released in the upcoming releases.#7164
f66b0c5Thanks @dyc3! - Added a new CSS parser optiontailwindDirectives. Enabling this option will allow all of Tailwind v4's syntax additions to be parsed and formatted by Biome.You can enable this by setting
css.parser.tailwindDirectivestotruein your Biome configuration.{ "css": { "parser": { "tailwindDirectives": true } } }#7669
6ed4d16Thanks @barklund! - React 19.2 support is now supported in Biome:useEffectEventlikeuseRefinuseExhaustiveDependencies<Activity />to known React APIs.#7702
28e8860Thanks @ematipico! - Added experimental full support for HTML, Vue, Svelte and Astro files. In this release, the HTML parserhas been enhanced, and it's now able to parse
.vue,.svelteand.astrofiles.This means that now Biome is able to lint and format the JavaScript (TypeScript), HTML and CSS code that is contained in these files.
Now that the main architecture is stable and working, in the upcoming patches and minors we will also fix possible inaccuracies and edge cases coming from existing lint rules, such as
noUnusedVariablesinside<script>blocks or frontmatter.The support is considered experimental because there might be cases that aren't fine-parsed yet, hence causing possible inaccuracies when it comes to formatting and linting.
#7599
09445c8Thanks @anaisbetts! - #### lineEnding has a new optionautoThe option
lineEndingnow has a variant calledautoto match the operating system's expectedline-ending style: on Windows, this will be CRLF (
\r\n), and on macOS / Linux, this willbe LF (
\n).This allows for cross-platform projects that use Biome not to have to
force one option or the other, which aligns better with Git's default behavior
on these platforms.
Example usage:
{ "formatter": { "lineEnding": "auto" } }#7392
e4feb8eThanks @ematipico! - Added new capabilities to the CLI arguments--skipand--only, available to thebiome lintcommand.--skipand--onlycan now accept domain names; when provided, Biome will run or skip all the rules that belong to a certain domain.For example, the following command will only run the rules that belong to the next domain:
Another example, the following command will skip the rules that belong to the project domain:
#7702
28e8860Thanks @ematipico! - Added a new option calledhtml.interpolation. This option enables the parsing of text expressions (or interpolation) in HTML files.The following
file.htmlwill be correctly formatted:To note that
html.interpolationonly parses text expressions that are delimited by double curly braces ({{ }}). The content of expressions is parsed as normal text.Patch Changes
#7712
fcc9b42Thanks @minht11! - Added new ruleuseVueDefineMacrosOrderwhich allows enforcing specific order for Vue compiler macros.In this example, the rule will suggest moving
definePropsbeforedefineEmits:#7698
3b6f5e3Thanks @ematipico! - Fixed an issue where the JUnit reporter returned a zero-based location. Now the location returned is one-based.#7819
ef45056Thanks @ematipico! - Fixed #7788. Removes some error logging that were emitted when loading possible configuration files.#7593
e51dd55Thanks @arendjr! - Fixed an issue with thefiles.maxSizesetting. Previously the setting would always be looked up in the root settings, even in monorepos where a closerbiome.jsonis available. It now correctly uses the nearest configuration.#7825
ad55b35Thanks @Conaclos! - Fixed #7798. useNamingConvention no longer panics when it encounters a name that consists of a single dollar sign$that doesn't match a custom convention.#7764
93be2abThanks @gaauwe! - Fixed #6589: Biome now properly loads extension settings before loading the configuration file when opening a text document in the LSP server.v2.2.7Compare Source
Patch Changes
#7715
b622425Thanks @Netail! - Added the nursery rulenoEmptySource, disallowing meaningless js, css, json & graphql files to prevent codebase clutter.#7714
c7e5a14Thanks @MeGaNeKoS! - Increased the maximum line limit for noExcessiveLinesPerFunction from 255 to 65,535 to better support large JSX/front-end components.#5868
2db73aeThanks @bushuai! - Fixed #5856,noRedundantUseStrictnow keeps leading trivia#7756
d665c97Thanks @ematipico! - Improved the diagnostic message of the rulenoDuplicateTestHooks.modelcontextprotocol/typescript-sdk (@modelcontextprotocol/sdk)
v1.20.2Compare Source
What's Changed
New Contributors
Full Changelog: modelcontextprotocol/typescript-sdk@1.20.1...1.20.2
shikijs/shiki (@shikijs/rehype)
v3.14.0Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
sveltejs/kit (@sveltejs/kit)
v2.48.0Compare Source
Minor Changes
forkAPI when available (#14793)Patch Changes
settledinstead oftickin navigate (#14800)v2.47.3Compare Source
Patch Changes
fix: avoid hanging when
error()is used while streaming promises from a serverloadfunction (#14722)chore: treeshake load function code if we know it's unused (#14764)
fix:
RecursiveFormFieldstype for recursive or unknown schemas (#14734)fix: rework internal representation of form value to be
$state(#14771)TanStack/form (@tanstack/svelte-form)
v1.23.8Compare Source
Patch Changes
form-core: Optimise event client emissions and minor layout tweaks (#1758)
Updated dependencies [
94631cb]:vitejs/vite-plugin-react (@vitejs/plugin-react)
v5.1.0Compare Source
Add
@vitejs/plugin-react/preamblevirtual module for SSR HMR (#890)SSR applications can now initialize HMR runtime by importing
@vitejs/plugin-react/preambleat the top of their client entry instead of manually callingtransformIndexHtml. This simplifies SSR setup for applications that don't use thetransformIndexHtmlAPI.Fix raw Rolldown support for Rolldown 1.0.0-beta.44+ (#930)
Rolldown 1.0.0-beta.44+ removed the top-level
jsxoption in favor oftransform.jsx. This plugin now uses thetransform.jsxoption to support Rolldown 1.0.0-beta.44+.better-auth/better-auth (better-auth)
v1.3.32Compare Source
v1.3.31Compare Source
🐞 Bug Fixes
View changes on GitHub
v1.3.30Compare Source
🐞 Bug Fixes
View changes on GitHub
v1.3.29Compare Source
🚀 Features
search_pathconfiguration - by @okisdev in #5449 (cb15e)🐞 Bug Fixes
View changes on GitHub
capricorn86/happy-dom (happy-dom)
v20.0.8Compare Source
👷♂️ Patch fixes
previousSibling()andnextSibling()didn't work inHTMLSelectElementandHTMLFormElement- By @capricorn86 in task #1939<tr>) should be valid inside a<template>element - By @capricorn86 in task #1939lucide-icons/lucide (lucide-react)
v0.548.0: Version 0.548.0Compare Source
What's Changed
gamepad-directionalicon by @felipeajzanetti in #3693New Contributors
Full Changelog: lucide-icons/lucide@0.547.0...0.548.0
v0.547.0: Version 0.547.0Compare Source
What's Changed
<template>(#2635) by @KhalidAlansary in #3576birdhouseicon by @hieu-onefold in #3378New Contributors
Full Changelog: lucide-icons/lucide@0.546.0...0.547.0
nuxt/nuxt (nuxt)
v4.2.0Compare Source
👀 Highlights
We're excited to announce Nuxt 4.2, bringing new capabilities for better TypeScript DX, enhanced error handling, and improved control over data fetching! 🎉
🎯 Abort Control for Data Fetching
You can now pass an
AbortControllersignal directly touseAsyncDataanduseFetch, giving you fine-grained control over request cancellation (#32531).Th
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.